Random Access Procedure Based On Contention Resolution

ABSTRACT

A wireless device receives a random access response in response to transmitting a first random access preamble. A Msg3 message, including a wireless device identifier of the wireless device, is transmitted via an uplink grant comprised in the random access response. A contention resolution time window is started based on transmitting the Msg3 message. A contention resolution is determined to be unsuccessful in response to not receiving a response, including the wireless device identifier and corresponding to the Msg3 message, during the contention resolution time window. Based on the determining, a two-step random access procedure is performed including transmitting a message including: a second random access preamble via a random access channel resource, and a transport block via an uplink resource corresponding to the random access channel resource.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 16/584,073, filed Sep. 26, 2019, which claims the benefit of U.S. Provisional Application No. 62/737,849, filed Sep. 27, 2018, all of which are hereby incorporated by reference in their entireties.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Examples of several of the various embodiments of the present disclosure are described herein with reference to the drawings.

FIG. 1 is a diagram of an example RAN architecture as per an aspect of an embodiment of the present disclosure.

FIG. 2A is a diagram of an example user plane protocol stack as per an aspect of an embodiment of the present disclosure.

FIG. 2B is a diagram of an example control plane protocol stack as per an aspect of an embodiment of the present disclosure.

FIG. 3 is a diagram of an example wireless device and two base stations as per an aspect of an embodiment of the present disclosure.

FIG. 4A, FIG. 4B, FIG. 4C and FIG. 4D are example diagrams for uplink and downlink signal transmission as per an aspect of an embodiment of the present disclosure.

FIG. 5A is a diagram of an example uplink channel mapping and example uplink physical signals as per an aspect of an embodiment of the present disclosure.

FIG. 5B is a diagram of an example downlink channel mapping and example downlink physical signals as per an aspect of an embodiment of the present disclosure.

FIG. 6 is a diagram depicting an example frame structure as per an aspect of an embodiment of the present disclosure.

FIG. 7A and FIG. 7B are diagrams depicting example sets of OFDM subcarriers as per an aspect of an embodiment of the present disclosure.

FIG. 8 is a diagram depicting example OFDM radio resources as per an aspect of an embodiment of the present disclosure.

FIG. 9A is a diagram depicting an example CSI-RS and/or SS block transmission in a multi-beam system.

FIG. 9B is a diagram depicting an example downlink beam management procedure as per an aspect of an embodiment of the present disclosure.

FIG. 10 is an example diagram of configured BWPs as per an aspect of an embodiment of the present disclosure.

FIG. 11A, and FIG. 11B are diagrams of an example multi connectivity as per an aspect of an embodiment of the present disclosure.

FIG. 12 is a diagram of an example random access procedure as per an aspect of an embodiment of the present disclosure.

FIG. 13 is a structure of example MAC entities as per an aspect of an embodiment of the present disclosure.

FIG. 14 is a diagram of an example RAN architecture as per an aspect of an embodiment of the present disclosure.

FIG. 15 is a diagram of example RRC states as per an aspect of an embodiment of the present disclosure.

FIG. 16 is an example of a two-step RA procedure as per an aspect of an embodiment of the present disclosure.

FIG. 17A, FIG. 17B, and FIG. 17C are examples of radio resource allocations of a PRACH resource and one or more associated UL radio resources as per an aspect of an embodiment of the present disclosure.

FIG. 18 shows an example of ra-ssb-OccasionMaskIndex values as per an aspect of an embodiment of the present disclosure.

FIG. 19 is a diagram of example channel access priority class as per an aspect of an embodiment of the present disclosure.

FIG. 20A, FIG. 20B, and FIG. 20C are respectively examples of an RAR, a MAC subheader with backoff indicator, and a MAC subheader with RAPID as per an aspect of an embodiment of the present disclosure.

FIG. 21 is an example of one of MAC RAR formats as per an aspect of an embodiment of the present disclosure

FIG. 22 is an example RAR format as per an aspect of an embodiment of the present disclosure.

FIG. 23A and FIG. 23B are example RAR formats as per an aspect of an embodiment of the present disclosure.

FIG. 24 is an example of a coverage of a cell configured with a DL and two ULs as per an aspect of an embodiment of the present disclosure.

FIG. 25 is an example diagram of contention based and contention-free random access procedures with LBT as per an aspect of an embodiment of the present disclosure.

FIG. 26 is an example diagram of a two-step RA procedure with LBT as per an aspect of an embodiment of the present disclosure.

FIG. 27 is an example of radio resource allocation for a two-step RA procedure as per an aspect of an embodiment of the present disclosure.

FIG. 28 is an example of one or more LBTs performed for a two-step RA procedure as per an aspect of an embodiment of the present disclosure.

FIG. 29A and FIG. 29B are examples of one or more LBTs performed for a two-step RA procedure in an unlicensed band as per an aspect of an embodiment of the present disclosure.

FIG. 30 is an example of one or more PRACH occasion configurations as per an aspect of an embodiment of the present disclosure.

FIG. 31 is an example of one or more PRACH occasion configurations as per an aspect of an embodiment of the present disclosure.

FIG. 32A and FIG. 32B are examples of switching a type of RA procedure as per an aspect of an embodiment of the present disclosure.

FIG. 33 is an example of a RA type switching as per an aspect of an embodiment of the present disclosure.

FIG. 34 is an example of a RA type switching as per an aspect of an embodiment of the present disclosure.

FIG. 35 is a flowchart as per an aspect of an example embodiment of the present disclosure.

FIG. 36 is a flowchart as per an aspect of an example embodiment of the present disclosure.

FIG. 37 is a flowchart as per an aspect of an example embodiment of the present disclosure.

DETAILED DESCRIPTION OF EMBODIMENTS

Example embodiments of the present disclosure enable operation of bandwidth parts and carrier aggregation. Embodiments of the technology disclosed herein may be employed in the technical field of multicarrier communication systems. More particularly, the embodiments of the technology disclosed herein may relate to cell and bandwidth part activation/deactivation and/or bandwidth part switching in multicarrier communication systems.

The following Acronyms are used throughout the present disclosure:

3GPP 3rd Generation Partnership Project

5GC 5G Core Network

ACK Acknowledgement

AMF Access and Mobility Management Function

ARQ Automatic Repeat Request

AS Access Stratum

ASIC Application-Specific Integrated Circuit

BA Bandwidth Adaptation

BCCH Broadcast Control Channel

BCH Broadcast Channel

BPSK Binary Phase Shift Keying

BWP Bandwidth Part

CA Carrier Aggregation

CC Component Carrier

CCCH Common Control CHannel

CDMA Code Division Multiple Access

CN Core Network

CP Cyclic Prefix

CP-OFDM Cyclic Prefix- Orthogonal Frequency Division Multiplex

C-RNTI Cell-Radio Network Temporary Identifier

CS Configured Scheduling

CSI Channel State Information

CSI-RS Channel State Information-Reference Signal

CQI Channel Quality Indicator

CSS Common Search Space

CU Central Unit

DC Dual Connectivity

DCCH Dedicated Control CHannel

DCI Downlink Control Information

DL Downlink

DL-SCH Downlink Shared CHannel

DM-RS DeModulation Reference Signal

DRB Data Radio Bearer

DRX Discontinuous Reception

DTCH Dedicated Traffic CHannel

DU Distributed Unit

EPC Evolved Packet Core

E-UTRA Evolved UMTS Terrestrial Radio Access

E-UTRAN Evolvcd-Universal Terrestrial Radio Access Network

FDD Frequency Division Duplex

FPGA Field Programmable Gate Arrays

F1-C F1-Control plane

F1-U F1-User plane

gNB next generation Node B

HARQ Hybrid Automatic Repeat reQuest

HDL Hardware Description Languages

IE Information Element

IP Internet Protocol

LCID Logical Channel IDentifier

LTE Long Term Evolution

MAC Media Access Control

MCG Master Cell Group

MCS Modulation and Coding Scheme

McNB Master evolved Node B

MIB Master Information Block

MME Mobility Management Entity

MN Master Node

NACK Negative Acknowledgement

NAS Non-Access Stratum

NG CP Next Generation Control Plane

NGC Next Generation Core

NG-C NG-Control plane

ng-cNB next generation evolved Node B

NG-U NG-User plane

NR New Radio

NR MAC New Radio MAC

NRPDCP New Radio PDCP

NR PHY New Radio PHYsical

NR RLC New Radio RLC

NR RRC New Radio RRC

NSSAI Network Slice Selection Assistance Information

O&M Operation and Maintenance

OFDM Orthogonal Frequency Division Multiplexing

PBCH Physical Broadcast CHannel

PCC Primary Component Carrier

PCCH Paging Control CHannel

PCell Primary Cell

PCH Paging CHannel

PDCCH Physical Downlink Control CHannel

PDCP Packet Data Convergence Protocol

PDSCH Physical Downlink Shared CHannel

PDU Protocol Data Unit

PHICH Physical HARQ Indicator CHannel

PHY PHYsical

PLMN Public Land Mobile Network

PM I Precoding Matrix Indicaior

PR ACM Physical Random Access CHannel

PRB Physical Resource Block

PSCell Primary Secondary Cell

PSS Primary Synchronization Signal

pTAG primary Timing Advance Group

PT-RS Phase Tracking Reference Signal

PUCCH Physical Uplink Control CHannel

PUSCH Physical Uplink Shared CHannel

QAM Quadrature Amplitude Modulation

QFI Quality of Service Indicator

QoS Quality of Service

QPSK Quadrature Phase Shift Keying

RA Random Access

RACH Random Access CHannel

RAN Radio Access Network

RAT Radio Access Technology

RA-RNTI Random Access-Radio Network Temporary Identifier

RB Resource Blocks

RBG Resource Block Groups

RI Rank Indicator

RLC Radio Link Control

RRC Radio Resource Control

RS Reference Signal

RSRP Reference Signal Received Power SCC Secondary- Component Carrier SCell Secondary Cell SCG Secondary Cell Group SC-FDMA Single Carrier-Frequency Division Multiple Access SDAP Service Data Adaptation Protocol SDU Service Data Unit SeNB Secondary evolved Node B SFN System Frame Number S-GW Serving Gate Way SI System Information SIB System Information Block SMF Session Management Function SN Secondary Node SpCell Special Cell SRB Signaling Radio Bearer SRS Sounding Reference Signal SS Synchronization Signal SSS Secondary Synchronizat on Signal sTAG secondary Timing Advance Group TA Timing Advance TAG Timing Advance Group TAI Tracking Area Identifier TAT Time Alignment Timer TB Transport Block TC-RNTI Temporary Ccll-Radio Network Temporary Identifier TDD Time Division Duplex TDM A Time Division Multiple Access TTI Transmission Time Interval UCI Uplink Control Information UE User Equipment UL Uplink UL-SCH Uplink Shared CHannel UPF User Plane Function UPGW User Plane Gateway VHDL VHSIC Hardware Description Language

Xn-C Xn-Control plane

Xn-U Xn-User plane

Example embodiments of the disclosure may be implemented using various physical layer modulation and transmission mechanisms. Example transmission mechanisms may include, but are not limited to: Code Division Multiple Access (CDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Time Division Multiple Access (TDMA), Wavelet technologies, and/or the like. Hybrid transmission mechanisms such as TDMA/CDMA, and OFDM/CDMA may also be employed. Various modulation schemes may be applied for signal transmission in the physical layer. Examples of modulation schemes include, but are not limited to: phase, amplitude, code, a combination of these, and/or the like. An example radio transmission method may implement Quadrature Amplitude Modulation (QAM) using Binary Phase Shift Keying (BPSK), Quadrature Phase Shift Keying (QPSK), 16-QAM, 64-QAM, 256-QAM, and/or the like. Physical radio transmission may be enhanced by dynamically or semi-dynamically changing the modulation and coding scheme depending on transmission requirements and radio conditions.

FIG. 1 is an example Radio Access Network (RAN) architecture as per an aspect of an embodiment of the present disclosure. As illustrated in this example, a RAN node may be a next generation Node B (gNB) (e.g. 120A, 120B) providing New Radio (NR) user plane and control plane protocol terminations towards a first wireless device (e.g. 110A). In an example, a RAN node may be a next generation evolved Node B (ng-eNB) (e.g. 124A, 124B), providing Evolved UMTS Terrestrial Radio Access (E-UTRA) user plane and control plane protocol terminations towards a second wireless device (e.g. 110B). The first wireless device may communicate with a gNB over a Uu interface. The second wireless device may communicate with a ng-eNB over a Uu interface. In this disclosure, wireless device 110A and 110B are structurally similar to wireless device 110. Base stations 120A and/or 120B may be structurally similarly to base station 120. Base station 120 may comprise at least one of a gNB (e.g. 122A and/or 122B), ng-eNB (e.g. 124A and/or 124B), and or the like.

A gNB or an ng-eNB may host functions such as: radio resource management and scheduling, IP header compression, encryption and integrity protection of data, selection of Access and Mobility Management Function (AMF) at User Equipment (UE) attachment, routing of user plane and control plane data, connection setup and release, scheduling and transmission of paging messages (originated from the AMF), scheduling and transmission of system broadcast information (originated from the AMF or Operation and Maintenance (O&M)), measurement and measurement reporting configuration, transport level packet marking in the uplink, session management, support of network slicing, Quality of Service (QoS) flow management and mapping to data radio bearers, support of UEs in RRC_INACTIVE state, distribution function for Non-Access Stratum (NAS) messages, RAN sharing, and dual connectivity or tight interworking between NR and E-UTRA.

In an example, one or more gNBs and/or one or more ng-eNBs may be interconnected with each other by means of Xn interface. A gNB or an ng-eNB may be connected by means of NG interfaces to 5G Core Network (5GC). In an example, 5GC may comprise one or more AMF/User Plan Function (UPF) functions (e.g. 130A or 130B). A gNB or an ng-eNB may be connected to a UPF by means of an NG-User plane (NG-U) interface. The NG-U interface may provide delivery (e.g. non-guaranteed delivery) of user plane Protocol Data Units (PDUs) between a RAN node and the UPF. A gNB or an ng-eNB may be connected to an AMF by means of an NG-Control plane (NG-C) interface. The NG-C interface may provide, for example, NG interface management, UE context management, UE mobility management, transport of NAS messages, paging, PDU session management, configuration transfer and/or warning message transmission, combinations thereof, and/or the like.

In an example, a UPF may host functions such as anchor point for intra-/inter-Radio Access Technology (RAT) mobility (when applicable), external PDU session point of interconnect to data network, packet routing and forwarding, packet inspection and user plane part of policy rule enforcement, traffic usage reporting, uplink classifier to support routing traffic flows to a data network, branching point to support multi-homed PDU session, QoS handling for user plane, e.g. packet filtering, gating, Uplink (UL)/Downlink (DL) rate enforcement, uplink traffic verification (e.g. Service Data Flow (SDF) to QoS flow mapping), downlink packet buffering and/or downlink data notification triggering.

In an example, an AMF may host functions such as NAS signaling termination, NAS signaling security, Access Stratum (AS) security control, inter Core Network (CN) node signaling for mobility between 3^(rd) Generation Partnership Project (3GPP) access networks, idle mode UE reachability (e.g., control and execution of paging retransmission), registration area management, support of intra-system and inter-system mobility, access authentication, access authorization including check of roaming rights, mobility management control (subscription and policies), support of network slicing and/or Session Management Function (SMF) selection.

FIG. 2A is an example user plane protocol stack, where Service Data Adaptation Protocol (SDAP) (e.g. 211 and 221), Packet Data Convergence Protocol (PDCP) (e.g. 212 and 222), Radio Link Control (RLC) (e.g. 213 and 223) and Media Access Control (MAC) (e.g. 214 and 224) sublayers and Physical (PHY) (e.g. 215 and 225) layer may be terminated in wireless device (e.g. 110) and gNB (e.g. 120) on the network side. In an example, a PHY layer provides transport services to higher layers (e.g. MAC, RRC, etc.). In an example, services and functions of a MAC sublayer may comprise mapping between logical channels and transport channels, multiplexing/demultiplexing of MAC Service Data Units (SDUs) belonging to one or different logical channels into/from Transport Blocks (TB s) delivered to/from the PHY layer, scheduling information reporting, error correction through Hybrid Automatic Repeat request (HARQ) (e.g. one HARQ entity per carrier in case of Carrier Aggregation (CA)), priority handling between UEs by means of dynamic scheduling, priority handling between logical channels of one UE by means of logical channel prioritization, and/or padding. A MAC entity may support one or multiple numerologies and/or transmission timings. In an example, mapping restrictions in a logical channel prioritization may control which numerology and/or transmission timing a logical channel may use. In an example, an RLC sublayer may supports transparent mode (TM), unacknowledged mode (UM) and acknowledged mode (AM) transmission modes. The RLC configuration may be per logical channel with no dependency on numerologies and/or Transmission Time Interval (TTI) durations. In an example, Automatic Repeat Request (ARQ) may operate on any of the numerologies and/or TTI durations the logical channel is configured with. In an example, services and functions of the PDCP layer for the user plane may comprise sequence numbering, header compression and decompression, transfer of user data, reordering and duplicate detection, PDCP PDU routing (e.g. in case of split bearers), retransmission of PDCP SDUs, ciphering, deciphering and integrity protection, PDCP SDU discard, PDCP re-establishment and data recovery for RLC AM, and/or duplication of PDCP PDUs. In an example, services and functions of SDAP may comprise mapping between a QoS flow and a data radio bearer. In an example, services and functions of SDAP may comprise mapping Quality of Service Indicator (QFI) in DL and UL packets. In an example, a protocol entity of SDAP may be configured for an individual PDU session.

FIG. 2B is an example control plane protocol stack where PDCP (e.g. 233 and 242), RLC (e.g. 234 and 243) and MAC (e.g. 235 and 244) sublayers and PHY (e.g. 236 and 245) layer may be terminated in wireless device (e.g. 110) and gNB (e.g. 120) on a network side and perform service and functions described above. In an example, RRC (e.g. 232 and 241) may be terminated in a wireless device and a gNB on a network side. In an example, services and functions of RRC may comprise broadcast of system information related to AS and NAS, paging initiated by 5GC or RAN, establishment, maintenance and release of an RRC connection between the UE and RAN, security functions including key management, establishment, configuration, maintenance and release of Signaling Radio Bearers (SRBs) and Data Radio Bearers (DRBs), mobility functions, QoS management functions, UE measurement reporting and control of the reporting, detection of and recovery from radio link failure, and/or NAS message transfer to/from NAS from/to a UE. In an example, NAS control protocol (e.g. 231 and 251) may be terminated in the wireless device and AMF (e.g. 130) on a network side and may perform functions such as authentication, mobility management between a UE and a AMF for 3GPP access and non-3GPP access, and session management between a UE and a SMF for 3GPP access and non-3GPP access.

In an example, a base station may configure a plurality of logical channels for a wireless device. A logical channel in the plurality of logical channels may correspond to a radio bearer and the radio bearer may be associated with a QoS requirement. In an example, a base station may configure a logical channel to be mapped to one or more TTIs/numerologies in a plurality of TTIs/numerologies. The wireless device may receive a Downlink Control Information (DCI) via Physical Downlink Control CHannel (PDCCH) indicating an uplink grant. In an example, the uplink grant may be for a first TTI/numerology and may indicate uplink resources for transmission of a transport block. The base station may configure each logical channel in the plurality of logical channels with one or more parameters to be used by a logical channel prioritization procedure at the MAC layer of the wireless device. The one or more parameters may comprise priority, prioritized bit rate, etc. A logical channel in the plurality of logical channels may correspond to one or more buffers comprising data associated with the logical channel. The logical channel prioritization procedure may allocate the uplink resources to one or more first logical channels in the plurality of logical channels and/or one or more MAC Control Elements (CEs). The one or more first logical channels may be mapped to the first TTI/numerology. The MAC layer at the wireless device may multiplex one or more MAC CEs and/or one or more MAC SDUs (e.g., logical channel) in a MAC PDU (e.g., transport block). In an example, the MAC PDU may comprise a MAC header comprising a plurality of MAC sub-headers. A MAC sub-header in the plurality of MAC sub-headers may correspond to a MAC CE or a MAC SUD (logical channel) in the one or more MAC CEs and/or one or more MAC SDUs. In an example, a MAC CE or a logical channel may be configured with a Logical Channel IDentifier (LCID). In an example, LCID for a logical channel or a MAC CE may be fixed/pre-configured. In an example, LCID for a logical channel or MAC CE may be configured for the wireless device by the base station. The MAC sub-header corresponding to a MAC CE or a MAC SDU may comprise LCID associated with the MAC CE or the MAC SDU.

In an example, a base station may activate and/or deactivate and/or impact one or more processes (e.g., set values of one or more parameters of the one or more processes or start and/or stop one or more timers of the one or more processes) at the wireless device by employing one or more MAC commands. The one or more MAC commands may comprise one or more MAC control elements. In an example, the one or more processes may comprise activation and/or deactivation of PDCP packet duplication for one or more radio bearers. The base station may transmit a MAC CE comprising one or more fields, the values of the fields indicating activation and/or deactivation of PDCP duplication for the one or more radio bearers. In an example, the one or more processes may comprise Channel State Information (CSI) transmission of on one or more cells. The base station may transmit one or more MAC CEs indicating activation and/or deactivation of the CSI transmission on the one or more cells. In an example, the one or more processes may comprise activation or deactivation of one or more secondary cells. In an example, the base station may transmit a MA CE indicating activation or deactivation of one or more secondary cells. In an example, the base station may transmit one or more MAC CEs indicating starting and/or stopping one or more Discontinuous Reception (DRX) timers at the wireless device. In an example, the base station may transmit one or more MAC CEs indicating one or more timing advance values for one or more Timing Advance Groups (TAGs).

FIG. 3 is a block diagram of base stations (base station 1, 120A, and base station 2, 120B) and a wireless device 110. A wireless device may be called an UE. A base station may be called a NB, eNB, gNB, and/or ng-eNB. In an example, a wireless device and/or a base station may act as a relay node. The base station 1, 120A, may comprise at least one communication interface 320A (e.g. a wireless modem, an antenna, a wired modem, and/or the like), at least one processor 321A, and at least one set of program code instructions 323A stored in non-transitory memory 322A and executable by the at least one processor 321A. The base station 2, 120B, may comprise at least one communication interface 320B, at least one processor 321B, and at least one set of program code instructions 323B stored in non-transitory memory 322B and executable by the at least one processor 321B.

A base station may comprise many sectors for example: 1, 2, 3, 4, or 6 sectors. A base station may comprise many cells, for example, ranging from 1 to 50 cells or more. A cell may be categorized, for example, as a primary cell or secondary cell. At Radio Resource Control (RRC) connection establishment/re-establishment/handover, one serving cell may provide the NAS (non-access stratum) mobility information (e.g. Tracking Area Identifier (TAI)). At RRC connection re-establishment/handover, one serving cell may provide the security input. This cell may be referred to as the Primary Cell (PCell). In the downlink, a carrier corresponding to the PCell may be a DL Primary Component Carrier (PCC), while in the uplink, a carrier may be an UL PCC. Depending on wireless device capabilities, Secondary Cells (SCells) may be configured to form together with a PCell a set of serving cells. In a downlink, a carrier corresponding to an SCell may be a downlink secondary component carrier (DL SCC), while in an uplink, a carrier may be an uplink secondary component carrier (UL SCC). An SCell may or may not have an uplink carrier.

A cell, comprising a downlink carrier and optionally an uplink carrier, may be assigned a physical cell ID and a cell index. A carrier (downlink or uplink) may belong to one cell. The cell ID or cell index may also identify the downlink carrier or uplink carrier of the cell (depending on the context it is used). In the disclosure, a cell ID may be equally referred to a carrier ID, and a cell index may be referred to a carrier index. In an implementation, a physical cell ID or a cell index may be assigned to a cell. A cell ID may be determined using a synchronization signal transmitted on a downlink carrier. A cell index may be determined using RRC messages. For example, when the disclosure refers to a first physical cell ID for a first downlink carrier, the disclosure may mean the first physical cell ID is for a cell comprising the first downlink carrier. The same concept may apply to, for example, carrier activation. When the disclosure indicates that a first carrier is activated, the specification may equally mean that a cell comprising the first carrier is activated.

A base station may transmit to a wireless device one or more messages (e.g. RRC messages) comprising a plurality of configuration parameters for one or more cells. One or more cells may comprise at least one primary cell and at least one secondary cell. In an example, an RRC message may be broadcasted or unicasted to the wireless device. In an example, configuration parameters may comprise common parameters and dedicated parameters.

Services and/or functions of an RRC sublayer may comprise at least one of: broadcast of system information related to AS and NAS; paging initiated by 5GC and/or NG-RAN; establishment, maintenance, and/or release of an RRC connection between a wireless device and NG-RAN, which may comprise at least one of addition, modification and release of carrier aggregation; or addition, modification, and/or release of dual connectivity in NR or between E-UTRA and NR. Services and/or functions of an RRC sublayer may further comprise at least one of security functions comprising key management; establishment, configuration, maintenance, and/or release of Signaling Radio Bearers (SRBs) and/or Data Radio Bearers (DRBs); mobility functions which may comprise at least one of a handover (e.g. intra NR mobility or inter-RAT mobility) and a context transfer; or a wireless device cell selection and reselection and control of cell selection and reselection. Services and/or functions of an RRC sublayer may further comprise at least one of QoS management functions; a wireless device measurement configuration/reporting; detection of and/or recovery from radio link failure; or NAS message transfer to/from a core network entity (e.g. AMF, Mobility Management Entity (MME)) from/to the wireless device.

An RRC sublayer may support an RRC_Idle state, an RRC_Inactive state and/or an RRC_Connected state for a wireless device. In an RRC_Idle state, a wireless device may perform at least one of: Public Land Mobile Network (PLMN) selection; receiving broadcasted system information; cell selection/re-selection; monitoring/receiving a paging for mobile terminated data initiated by 5GC; paging for mobile terminated data area managed by 5GC; or DRX for CN paging configured via NAS. In an RRC_Inactive state, a wireless device may perform at least one of: receiving broadcasted system information; cell selection/re-selection; monitoring/receiving a RAN/CN paging initiated by NG-RAN/5GC; RAN-based notification area (RNA) managed by NG-RAN; or DRX for RAN/CN paging configured by NG-RAN/NAS. In an RRC_Idle state of a wireless device, a base station (e.g. NG-RAN) may keep a 5GC-NG-RAN connection (both C/U-planes) for the wireless device; and/or store a UE AS context for the wireless device. In an RRC_Connected state of a wireless device, a base station (e.g. NG-RAN) may perform at least one of: establishment of 5GC-NG-RAN connection (both C/U-planes) for the wireless device; storing a UE AS context for the wireless device; transmit/receive of unicast data to/from the wireless device; or network-controlled mobility based on measurement results received from the wireless device. In an RRC_Connected state of a wireless device, an NG-RAN may know a cell that the wireless device belongs to.

System information (SI) may be divided into minimum SI and other SI. The minimum SI may be periodically broadcast. The minimum SI may comprise basic information required for initial access and information for acquiring any other SI broadcast periodically or provisioned on-demand, i.e. scheduling information. The other SI may either be broadcast, or be provisioned in a dedicated manner, either triggered by a network or upon request from a wireless device. A minimum SI may be transmitted via two different downlink channels using different messages (e.g. MasterInformationBlock and SysternInformationBlockType1). Another SI may be transmitted via SystemInformationBlockType2. For a wireless device in an RRC_Connected state, dedicated RRC signaling may be employed for the request and delivery of the other SI. For the wireless device in the RRC_Idle state and/or the RRC_Inactive state, the request may trigger a random-access procedure.

A wireless device may report its radio access capability information which may be static. A base station may request what capabilities for a wireless device to report based on band information. When allowed by a network, a temporary capability restriction request may be sent by the wireless device to signal the limited availability of some capabilities (e.g. due to hardware sharing, interference or overheating) to the base station. The base station may confirm or reject the request. The temporary capability restriction may be transparent to 5GC (e.g., static capabilities may be stored in 5GC).

When CA is configured, a wireless device may have an RRC connection with a network. At RRC connection establishment/re-establishment/handover procedure, one serving cell may provide NAS mobility information, and at RRC connection re-establishment/handover, one serving cell may provide a security input. This cell may be referred to as the PCell. Depending on the capabilities of the wireless device, SCells may be configured to form together with the PCell a set of serving cells. The configured set of serving cells for the wireless device may comprise one PCell and one or more SCells.

The reconfiguration, addition and removal of SCells may be performed by RRC. At intra-NR handover, RRC may also add, remove, or reconfigure SCells for usage with the target PCell. When adding a new SCell, dedicated RRC signaling may be employed to send all required system information of the SCell i.e. while in connected mode, wireless devices may not need to acquire broadcasted system information directly from the SCells.

The purpose of an RRC connection reconfiguration procedure may be to modify an RRC connection, (e.g. to establish, modify and/or release RBs, to perform handover, to setup, modify, and/or release measurements, to add, modify, and/or release SCells and cell groups). As part of the RRC connection reconfiguration procedure, NAS dedicated information may be transferred from the network to the wireless device. The RRCConnectionReconfiguration message may be a command to modify an RRC connection. It may convey information for measurement configuration, mobility control, radio resource configuration (e.g. RBs, MAC main configuration and physical channel configuration) comprising any associated dedicated NAS information and security configuration. If the received RRC Connection Reconfiguration message includes the sCellToReleaseList, the wireless device may perform an SCell release. If the received RRC Connection Reconfiguration message includes the sCellToAddModList, the wireless device may perform SCell additions or modification.

An RRC connection establishment (or reestablishment, resume) procedure may be to establish (or reestablish, resume) an RRC connection. an RRC connection establishment procedure may comprise SRB1 establishment. The RRC connection establishment procedure may be used to transfer the initial NAS dedicated information/message from a wireless device to E-UTRAN. The RRCConnectionReestablishment message may be used to re-establish SRB1.

A measurement report procedure may be to transfer measurement results from a wireless device to NG-RAN. The wireless device may initiate a measurement report procedure after successful security activation. A measurement report message may be employed to transmit measurement results.

The wireless device 110 may comprise at least one communication interface 310 (e.g. a wireless modem, an antenna, and/or the like), at least one processor 314, and at least one set of program code instructions 316 stored in non-transitory memory 315 and executable by the at least one processor 314. The wireless device 110 may further comprise at least one of at least one speaker/microphone 311, at least one keypad 312, at least one display/touchpad 313, at least one power source 317, at least one global positioning system (GPS) chipset 318, and other peripherals 319.

The processor 314 of the wireless device 110, the processor 321A of the base station 1 120A, and/or the processor 321B of the base station 2 120B may comprise at least one of a general-purpose processor, a digital signal processor (DSP), a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) and/or other programmable logic device, discrete gate and/or transistor logic, discrete hardware components, and the like. The processor 314 of the wireless device 110, the processor 321A in base station 1 120A, and/or the processor 321B in base station 2 120B may perform at least one of signal coding/processing, data processing, power control, input/output processing, and/or any other functionality that may enable the wireless device 110, the base station 1 120A and/or the base station 2 120B to operate in a wireless environment.

The processor 314 of the wireless device 110 may be connected to the speaker/microphone 311, the keypad 312, and/or the display/touchpad 313. The processor 314 may receive user input data from and/or provide user output data to the speaker/microphone 311, the keypad 312, and/or the display/touchpad 313. The processor 314 in the wireless device 110 may receive power from the power source 317 and/or may be configured to distribute the power to the other components in the wireless device 110. The power source 317 may comprise at least one of one or more dry cell batteries, solar cells, fuel cells, and the like. The processor 314 may be connected to the GPS chipset 318. The GPS chipset 318 may be configured to provide geographic location information of the wireless device 110.

The processor 314 of the wireless device 110 may further be connected to other peripherals 319, which may comprise one or more software and/or hardware modules that provide additional features and/or functionalities. For example, the peripherals 319 may comprise at least one of an accelerometer, a satellite transceiver, a digital camera, a universal serial bus (USB) port, a hands-free headset, a frequency modulated (FM) radio unit, a media player, an Internet browser, and the like.

The communication interface 320A of the base station 1, 120A, and/or the communication interface 320B of the base station 2, 120B, may be configured to communicate with the communication interface 310 of the wireless device 110 via a wireless link 330A and/or a wireless link 330B respectively. In an example, the communication interface 320A of the base station 1, 120A, may communicate with the communication interface 320B of the base station 2 and other RAN and core network nodes.

The wireless link 330A and/or the wireless link 330B may comprise at least one of a bi-directional link and/or a directional link. The communication interface 310 of the wireless device 110 may be configured to communicate with the communication interface 320A of the base station 1 120A and/or with the communication interface 320B of the base station 2 120B. The base station 1 120A and the wireless device 110 and/or the base station 2 120B and the wireless device 110 may be configured to send and receive transport blocks via the wireless link 330A and/or via the wireless link 330B, respectively. The wireless link 330A and/or the wireless link 330B may employ at least one frequency carrier. According to some of various aspects of embodiments, transceiver(s) may be employed. A transceiver may be a device that comprises both a transmitter and a receiver. Transceivers may be employed in devices such as wireless devices, base stations, relay nodes, and/or the like. Example embodiments for radio technology implemented in the communication interface 310, 320A, 320B and the wireless link 330A, 330B are illustrated in FIG. 4A, FIG. 4B, FIG. 4C, FIG. 4D, FIG. 6, FIG. 7A, FIG. 7B, FIG. 8, and associated text.

In an example, other nodes in a wireless network (e.g. AMF, UPF, SMF, etc.) may comprise one or more communication interfaces, one or more processors, and memory storing instructions.

A node (e.g. wireless device, base station, AMF, SMF, UPF, servers, switches, antennas, and/or the like) may comprise one or more processors, and memory storing instructions that when executed by the one or more processors causes the node to perform certain processes and/or functions. Example embodiments may enable operation of single-carrier and/or multi-carrier communications. Other example embodiments may comprise a non-transitory tangible computer readable media comprising instructions executable by one or more processors to cause operation of single-carrier and/or multi-carrier communications. Yet other example embodiments may comprise an article of manufacture that comprises a non-transitory tangible computer readable machine-accessible medium having instructions encoded thereon for enabling programmable hardware to cause a node to enable operation of single-carrier and/or multi-carrier communications. The node may include processors, memory, interfaces, and/or the like.

An interface may comprise at least one of a hardware interface, a firmware interface, a software interface, and/or a combination thereof. The hardware interface may comprise connectors, wires, electronic devices such as drivers, amplifiers, and/or the like. The software interface may comprise code stored in a memory device to implement protocol(s), protocol layers, communication drivers, device drivers, combinations thereof, and/or the like. The firmware interface may comprise a combination of embedded hardware and code stored in and/or in communication with a memory device to implement connections, electronic device operations, protocol(s), protocol layers, communication drivers, device drivers, hardware operations, combinations thereof, and/or the like.

FIG. 4A, FIG. 4B, FIG. 4C and FIG. 4D are example diagrams for uplink and downlink signal transmission as per an aspect of an embodiment of the present disclosure. FIG. 4A shows an example uplink transmitter for at least one physical channel. A baseband signal representing a physical uplink shared channel may perform one or more functions. The one or more functions may comprise at least one of: scrambling; modulation of scrambled bits to generate complex-valued symbols; mapping of the complex-valued modulation symbols onto one or several transmission layers; transform precoding to generate complex-valued symbols; precoding of the complex-valued symbols; mapping of precoded complex-valued symbols to resource elements; generation of complex-valued time-domain Single Carrier-Frequency Division Multiple Access (SC-FDMA) or CP-OFDM signal for an antenna port; and/or the like. In an example, when transform precoding is enabled, a SC-FDMA signal for uplink transmission may be generated. In an example, when transform precoding is not enabled, an CP-OFDM signal for uplink transmission may be generated by FIG. 4A. These functions are illustrated as examples and it is anticipated that other mechanisms may be implemented in various embodiments.

An example structure for modulation and up-conversion to the carrier frequency of the complex-valued SC-FDMA or CP-OFDM baseband signal for an antenna port and/or the complex-valued Physical Random Access CHannel (PRACH) baseband signal is shown in FIG. 4B. Filtering may be employed prior to transmission.

An example structure for downlink transmissions is shown in FIG. 4C. The baseband signal representing a downlink physical channel may perform one or more functions. The one or more functions may comprise: scrambling of coded bits in a codeword to be transmitted on a physical channel; modulation of scrambled bits to generate complex-valued modulation symbols; mapping of the complex-valued modulation symbols onto one or several transmission layers; precoding of the complex-valued modulation symbols on a layer for transmission on the antenna ports; mapping of complex-valued modulation symbols for an antenna port to resource elements; generation of complex-valued time-domain OFDM signal for an antenna port; and/or the like. These functions are illustrated as examples and it is anticipated that other mechanisms may be implemented in various embodiments.

In an example, a base station may transmit a first symbol and a second symbol on an antenna port, to a wireless device. The wireless device may infer the channel (e.g., fading gain, multipath delay, etc.) for conveying the second symbol on the antenna port, from the channel for conveying the first symbol on the antenna port. In an example, a first antenna port and a second antenna port may be quasi co-located if one or more large-scale properties of the channel over which a first symbol on the first antenna port is conveyed may be inferred from the channel over which a second symbol on a second antenna port is conveyed. The one or more large-scale properties may comprise at least one of: delay spread; doppler spread; doppler shift; average gain; average delay; and/or spatial Receiving (Rx) parameters.

An example modulation and up-conversion to the carrier frequency of the complex-valued OFDM baseband signal for an antenna port is shown in FIG. 4D. Filtering may be employed prior to transmission.

FIG. 5A is a diagram of an example uplink channel mapping and example uplink physical signals. FIG. 5B is a diagram of an example downlink channel mapping and a downlink physical signals. In an example, a physical layer may provide one or more information transfer services to a MAC and/or one or more higher layers. For example, the physical layer may provide the one or more information transfer services to the MAC via one or more transport channels. An information transfer service may indicate how and with what characteristics data are transferred over the radio interface.

In an example embodiment, a radio network may comprise one or more downlink and/or uplink transport channels. For example, a diagram in FIG. 5A shows example uplink transport channels comprising Uplink-Shared CHannel (UL-SCH) 501 and Random Access CHannel (RACH) 502. A diagram in FIG. 5B shows example downlink transport channels comprising Downlink-Shared CHannel (DL-SCH) 511, Paging CHannel (PCH) 512, and Broadcast CHannel (BCH) 513. A transport channel may be mapped to one or more corresponding physical channels. For example, UL-SCH 501 may be mapped to Physical Uplink Shared CHannel (PUSCH) 503. RACH 502 may be mapped to PRACH 505. DL-SCH 511 and PCH 512 may be mapped to Physical Downlink Shared CHannel (PDSCH) 514. BCH 513 may be mapped to Physical Broadcast CHannel (PBCH) 516.

There may be one or more physical channels without a corresponding transport channel. The one or more physical channels may be employed for Uplink Control Information (UCI) 509 and/or Downlink Control Information (DCI) 517. For example, Physical Uplink Control CHannel (PUCCH) 504 may carry UCI 509 from a UE to a base station. For example, Physical Downlink Control CHannel (PDCCH) 515 may carry DCI 517 from a base station to a UE. NR may support UCI 509 multiplexing in PUSCH 503 when UCI 509 and PUSCH 503 transmissions may coincide in a slot at least in part. The UCI 509 may comprise at least one of CSI, Acknowledgement (ACK)/Negative Acknowledgement (NACK), and/or scheduling request. The DCI 517 on PDCCH 515 may indicate at least one of following: one or more downlink assignments and/or one or more uplink scheduling grants

In uplink, a UE may transmit one or more Reference Signals (RSs) to a base station. For example, the one or more RSs may be at least one of Demodulation-RS (DM-RS) 506, Phase Tracking-RS (PT-RS) 507, and/or Sounding RS (SRS) 508. In downlink, a base station may transmit (e.g., unicast, multicast, and/or broadcast) one or more RSs to a UE. For example, the one or more RSs may be at least one of Primary Synchronization Signal (PSS)/Secondary Synchronization Signal (SSS) 521, CSI-RS 522, DM-RS 523, and/or PT-RS 524.

In an example, a UE may transmit one or more uplink DM-RSs 506 to a base station for channel estimation, for example, for coherent demodulation of one or more uplink physical channels (e.g., PUSCH 503 and/or PUCCH 504). For example, a UE may transmit a base station at least one uplink DM-RS 506 with PUSCH 503 and/or PUCCH 504, wherein the at least one uplink DM-RS 506 may be spanning a same frequency range as a corresponding physical channel. In an example, a base station may configure a UE with one or more uplink DM-RS configurations. At least one DM-RS configuration may support a front-loaded DM-RS pattern. A front-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1 or 2 adjacent OFDM symbols). One or more additional uplink DM-RS may be configured to transmit at one or more symbols of a PUSCH and/or PUCCH. A base station may semi-statically configure a UE with a maximum number of front-loaded DM-RS symbols for PUSCH and/or PUCCH. For example, a UE may schedule a single-symbol DM-RS and/or double symbol DM-RS based on a maximum number of front-loaded DM-RS symbols, wherein a base station may configure the UE with one or more additional uplink DM-RS for PUSCH and/or PUCCH. A new radio network may support, e.g., at least for CP-OFDM, a common DM-RS structure for DL and UL, wherein a DM-RS location, DM-RS pattern, and/or scrambling sequence may be same or different.

In an example, whether uplink PT-RS 507 is present or not may depend on a RRC configuration. For example, a presence of uplink PT-RS may be UE-specifically configured. For example, a presence and/or a pattern of uplink PT-RS 507 in a scheduled resource may be UE-specifically configured by a combination of RRC signaling and/or association with one or more parameters employed for other purposes (e.g., Modulation and Coding Scheme (MCS)) which may be indicated by DCI. When configured, a dynamic presence of uplink PT-RS 507 may be associated with one or more DCI parameters comprising at least MCS. A radio network may support plurality of uplink PT-RS densities defined in time/frequency domain. When present, a frequency domain density may be associated with at least one configuration of a scheduled bandwidth. A UE may assume a same precoding for a DMRS port and a PT-RS port. A number of PT-RS ports may be fewer than a number of DM-RS ports in a scheduled resource. For example, uplink PT-RS 507 may be confined in the scheduled time/frequency duration for a UE.

In an example, a UE may transmit SRS 508 to a base station for channel state estimation to support uplink channel dependent scheduling and/or link adaptation. For example, SRS 508 transmitted by a UE may allow for a base station to estimate an uplink channel state at one or more different frequencies. A base station scheduler may employ an uplink channel state to assign one or more resource blocks of good quality for an uplink PUSCH transmission from a UE. A base station may semi-statically configure a UE with one or more SRS resource sets. For an SRS resource set, a base station may configure a UE with one or more SRS resources. An SRS resource set applicability may be configured by a higher layer (e.g., RRC) parameter. For example, when a higher layer parameter indicates beam management, a SRS resource in each of one or more SRS resource sets may be transmitted at a time instant. A UE may transmit one or more SRS resources in different SRS resource sets simultaneously. A new radio network may support aperiodic, periodic and/or semi-persistent SRS transmissions. A UE may transmit SRS resources based on one or more trigger types, wherein the one or more trigger types may comprise higher layer signaling (e.g., RRC) and/or one or more DCI formats (e.g., at least one DCI format may be employed for a UE to select at least one of one or more configured SRS resource sets. An SRS trigger type 0 may refer to an SRS triggered based on a higher layer signaling. An SRS trigger type 1 may refer to an SRS triggered based on one or more DCI formats. In an example, when PUSCH 503 and SRS 508 are transmitted in a same slot, a UE may be configured to transmit SRS 508 after a transmission of PUSCH 503 and corresponding uplink DM-RS 506.

In an example, a base station may semi-statically configure a UE with one or more SRS configuration parameters indicating at least one of following: a SRS resource configuration identifier, a number of SRS ports, time domain behavior of SRS resource configuration (e.g., an indication of periodic, semi-persistent, or aperiodic SRS), slot (mini-slot, and/or subframe) level periodicity and/or offset for a periodic and/or aperiodic SRS resource, a number of OFDM symbols in a SRS resource, starting OFDM symbol of a SRS resource, a SRS bandwidth, a frequency hopping bandwidth, a cyclic shift, and/or a SRS sequence ID.

In an example, in a time domain, an SS/PBCH block may comprise one or more OFDM symbols (e.g., 4 OFDM symbols numbered in increasing order from 0 to 3) within the SS/PBCH block. An SS/PBCH block may comprise PSS/SSS 521 and PBCH 516. In an example, in the frequency domain, an SS/PBCH block may comprise one or more contiguous subcarriers (e.g., 240 contiguous subcarriers with the subcarriers numbered in increasing order from 0 to 239) within the SS/PBCH block. For example, a PSS/SSS 521 may occupy 1 OFDM symbol and 127 subcarriers. For example, PBCH 516 may span across 3 OFDM symbols and 240 subcarriers. A UE may assume that one or more SS/PBCH blocks transmitted with a same block index may be quasi co-located, e.g., with respect to Doppler spread, Doppler shift, average gain, average delay, and spatial Rx parameters. A UE may not assume quasi co-location for other SS/PBCH block transmissions. A periodicity of an SS/PBCH block may be configured by a radio network (e.g., by an RRC signaling) and one or more time locations where the SS/PBCH block may be sent may be determined by sub-carrier spacing. In an example, a UE may assume a band-specific sub-carrier spacing for an SS/PBCH block unless a radio network has configured a UE to assume a different sub-carrier spacing.

In an example, downlink CSI-RS 522 may be employed for a UE to acquire channel state information. A radio network may support periodic, aperiodic, and/or semi-persistent transmission of downlink CSI-RS 522. For example, a base station may semi-statically configure and/or reconfigure a UE with periodic transmission of downlink CSI-RS 522. A configured CSI-RS resources may be activated ad/or deactivated. For semi-persistent transmission, an activation and/or deactivation of CSI-RS resource may be triggered dynamically. In an example, CSI-RS configuration may comprise one or more parameters indicating at least a number of antenna ports. For example, a base station may configure a UE with 32 ports. A base station may semi-statically configure a UE with one or more CSI-RS resource sets. One or more CSI-RS resources may be allocated from one or more CSI-RS resource sets to one or more UEs. For example, a base station may semi-statically configure one or more parameters indicating CSI RS resource mapping, for example, time-domain location of one or more CSI-RS resources, a bandwidth of a CSI-RS resource, and/or a periodicity. In an example, a UE may be configured to employ a same OFDM symbols for downlink CSI-RS 522 and control resource set (coreset) when the downlink CSI-RS 522 and coreset are spatially quasi co-located and resource elements associated with the downlink CSI-RS 522 are the outside of PRBs configured for coreset. In an example, a UE may be configured to employ a same OFDM symbols for downlink CSI-RS 522 and SSB/PBCH when the downlink CSI-RS 522 and SSB/PBCH are spatially quasi co-located and resource elements associated with the downlink CSI-RS 522 are the outside of PRBs configured for SSB/PBCH.

In an example, a UE may transmit one or more downlink DM-RS s 523 to a base station for channel estimation, for example, for coherent demodulation of one or more downlink physical channels (e.g., PDSCH 514). For example, a radio network may support one or more variable and/or configurable DM-RS patterns for data demodulation. At least one downlink DM-RS configuration may support a front-loaded DM-RS pattern. A front-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1 or 2 adjacent OFDM symbols). A base station may semi-statically configure a UE with a maximum number of front-loaded DM-RS symbols for PDSCH 514. For example, a DM-RS configuration may support one or more DM-RS ports. For example, for single user-MIMO, a DM-RS configuration may support at least 8 orthogonal downlink DM-RS ports. For example, for multiuser-MIMO, a DM-RS configuration may support 12 orthogonal downlink DM-RS ports. A radio network may support, e.g., at least for CP-OFDM, a common DM-RS structure for DL and UL, wherein a DM-RS location, DM-RS pattern, and/or scrambling sequence may be same or different.

In an example, whether downlink PT-RS 524 is present or not may depend on a RRC configuration. For example, a presence of downlink PT-RS 524 may be UE-specifically configured. For example, a presence and/or a pattern of downlink PT-RS 524 in a scheduled resource may be UE-specifically configured by a combination of RRC signaling and/or association with one or more parameters employed for other purposes (e.g., MCS) which may be indicated by DCI. When configured, a dynamic presence of downlink PT-RS 524 may be associated with one or more DCI parameters comprising at least MCS. A radio network may support plurality of PT-RS densities defined in time/frequency domain. When present, a frequency domain density may be associated with at least one configuration of a scheduled bandwidth. A UE may assume a same precoding for a DMRS port and a PT-RS port. A number of PT-RS ports may be fewer than a number of DM-RS ports in a scheduled resource. For example, downlink PT-RS 524 may be confined in the scheduled time/frequency duration for a UE.

FIG. 6 is a diagram depicting an example frame structure for a carrier as per an aspect of an embodiment of the present disclosure. A multicarrier OFDM communication system may include one or more carriers, for example, ranging from 1 to 32 carriers, in case of carrier aggregation, or ranging from 1 to 64 carriers, in case of dual connectivity. Different radio frame structures may be supported (e.g., for FDD and for TDD duplex mechanisms). FIG. 6 shows an example frame structure. Downlink and uplink transmissions may be organized into radio frames 601. In this example, radio frame duration is 10 ms. In this example, a 10 ms radio frame 601 may be divided into ten equally sized subframes 602 with 1 ms duration. Subframe(s) may comprise one or more slots (e.g. slots 603 and 605) depending on subcarrier spacing and/or CP length. For example, a subframe with 15 kHz, 30 kHz, 60 kHz, 120 kHz, 240 kHz and 480 kHz subcarrier spacing may comprise one, two, four, eight, sixteen and thirty-two slots, respectively. In FIG. 6, a subframe may be divided into two equally sized slots 603 with 0.5 ms duration. For example, 10 subframes may be available for downlink transmission and 10 subframes may be available for uplink transmissions in a 10 ms interval. Uplink and downlink transmissions may be separated in the frequency domain. Slot(s) may include a plurality of OFDM symbols 604. The number of OFDM symbols 604 in a slot 605 may depend on the cyclic prefix length. For example, a slot may be 14 OFDM symbols for the same subcarrier spacing of up to 480 kHz with normal CP. A slot may be 12 OFDM symbols for the same subcarrier spacing of 60 kHz with extended CP. A slot may contain downlink, uplink, or a downlink part and an uplink part and/or alike.

FIG. 7A is a diagram depicting example sets of OFDM subcarriers as per an aspect of an embodiment of the present disclosure. In the example, a gNB may communicate with a wireless device with a carrier with an example channel bandwidth 700. Arrow(s) in the diagram may depict a subcarrier in a multicarrier OFDM system. The OFDM system may use technology such as OFDM technology, SC-FDMA technology, and/or the like. In an example, an arrow 701 shows a subcarrier transmitting information symbols. In an example, a subcarrier spacing 702, between two contiguous subcarriers in a carrier, may be any one of 15 KHz, 30 KHz, 60 KHz, 120 KHz, 240 KHz etc. In an example, different subcarrier spacing may correspond to different transmission numerologies. In an example, a transmission numerology may comprise at least: a numerology index; a value of subcarrier spacing; a type of cyclic prefix (CP). In an example, a gNB may transmit to/receive from a UE on a number of subcarriers 703 in a carrier. In an example, a bandwidth occupied by a number of subcarriers 703 (transmission bandwidth) may be smaller than the channel bandwidth 700 of a carrier, due to guard band 704 and 705. In an example, a guard band 704 and 705 may be used to reduce interference to and from one or more neighbor carriers. A number of subcarriers (transmission bandwidth) in a carrier may depend on the channel bandwidth of the carrier and the subcarrier spacing. For example, a transmission bandwidth, for a carrier with 20 MHz channel bandwidth and 15 KHz subcarrier spacing, may be in number of 1024 subcarriers.

In an example, a gNB and a wireless device may communicate with multiple CCs when configured with CA. In an example, different component carriers may have different bandwidth and/or subcarrier spacing, if CA is supported. In an example, a gNB may transmit a first type of service to a UE on a first component carrier. The base station may transmit a second type of service to the UE on a second component carrier. Different type of services may have different service requirement (e.g., data rate, latency, reliability), which may be suitable for transmission via different component carrier having different subcarrier spacing and/or bandwidth. FIG. 7B shows an example embodiment. A first component carrier may comprise a first number of subcarriers 706 with a first subcarrier spacing 709. A second component carrier may comprise a second number of subcarriers 707 with a second subcarrier spacing 710. A third component carrier may comprise a third number of subcarriers 708 with a third subcarrier spacing 711. Carriers in a multicarrier OFDM communication system may be contiguous carriers, non-contiguous carriers, or a combination of both contiguous and non-contiguous carriers.

FIG. 8 is a diagram depicting OFDM radio resources as per an aspect of an embodiment of the present disclosure. In an example, a carrier may have a transmission bandwidth 801. In an example, a resource grid may be in a structure of frequency domain 802 and time domain 803. In an example, a resource grid may comprise a first number of OFDM symbols in a subframe and a second number of resource blocks, starting from a common resource block indicated by higher-layer signaling (e.g. RRC signaling), for a transmission numerology and a carrier. In an example, in a resource grid, a resource unit identified by a subcarrier index and a symbol index may be a resource element 805. In an example, a subframe may comprise a first number of OFDM symbols 807 depending on a numerology associated with a carrier. For example, when a subcarrier spacing of a numerology of a carrier is 15 KHz, a subframe may have 14 OFDM symbols for a carrier. When a subcarrier spacing of a numerology is 30 KHz, a subframe may have 28 OFDM symbols. When a subcarrier spacing of a numerology is 60 Khz, a subframe may have 56 OFDM symbols, etc. In an example, a second number of resource blocks comprised in a resource grid of a carrier may depend on a bandwidth and a numerology of the carrier.

As shown in FIG. 8, a resource block 806 may comprise 12 subcarriers. In an example, multiple resource blocks may be grouped into a Resource Block Group (RBG) 804. In an example, a size of a RBG may depend on at least one of: a RRC message indicating a RBG size configuration; a size of a carrier bandwidth; or a size of a bandwidth part of a carrier. In an example, a carrier may comprise multiple bandwidth parts. A first bandwidth part of a carrier may have different frequency location and/or bandwidth from a second bandwidth part of the carrier.

In an example, a gNB may transmit a downlink control information comprising a downlink or uplink resource block assignment to a wireless device. A base station may transmit to or receive from, a wireless device, data packets (e.g. transport blocks) scheduled and transmitted via one or more resource blocks and one or more slots according to parameters in a downlink control information and/or RRC message(s). In an example, a starting symbol relative to a first slot of the one or more slots may be indicated to the wireless device. In an example, a gNB may transmit to or receive from, a wireless device, data packets scheduled on one or more RB Gs and one or more slots.

In an example, a gNB may transmit a downlink control information comprising a downlink assignment to a wireless device via one or more PDCCHs. The downlink assignment may comprise parameters indicating at least modulation and coding format; resource allocation; and/or HARQ information related to DL-SCH. In an example, a resource allocation may comprise parameters of resource block allocation; and/or slot allocation. In an example, a gNB may dynamically allocate resources to a wireless device via a Cell-Radio Network Temporary Identifier (C-RNTI) on one or more PDCCHs. The wireless device may monitor the one or more PDCCHs in order to find possible allocation when its downlink reception is enabled. The wireless device may receive one or more downlink data package on one or more PDSCH scheduled by the one or more PDCCHs, when successfully detecting the one or more PDCCHs.

In an example, a gNB may allocate Configured Scheduling (CS) resources for down link transmission to a wireless device. The base station may transmit one or more RRC messages indicating a periodicity of the CS grant. The base station may transmit a DCI via a PDCCH addressed to a Configured Scheduling-RNTI (CS-RNTI) activating the CS resources. The DCI may comprise parameters indicating that the downlink grant is a CS grant. The CS grant may be implicitly reused according to the periodicity defined by the one or more RRC messages, until deactivated.

In an example, a gNB may transmit a downlink control information comprising an uplink grant to a wireless device via one or more PDCCHs. The uplink grant may comprise parameters indicating at least modulation and coding format; resource allocation; and/or HARQ information related to UL-SCH. In an example, a resource allocation may comprise parameters of resource block allocation; and/or slot allocation. In an example, a gNB may dynamically allocate resources to a wireless device via a C-RNTI on one or more PDCCHs. The wireless device may monitor the one or more PDCCHs in order to find possible resource allocation. The wireless device may transmit one or more uplink data package via one or more PUSCH scheduled by the one or more PDCCHs, when successfully detecting the one or more PDCCHs.

In an example, a gNB may allocate CS resources for uplink data transmission to a wireless device. The base station may transmit one or more RRC messages indicating a periodicity of the CS grant. The base station may transmit a DCI via a PDCCH addressed to a CS-RNTI activating the CS resources. The DCI may comprise parameters indicating that the uplink grant is a CS grant. The CS grant may be implicitly reused according to the periodicity defined by the one or more RRC message, until deactivated.

In an example, a base station may transmit DCl/control signaling via PDCCH. The DCI may take a format in a plurality of formats. A DCI may comprise downlink and/or uplink scheduling information (e.g., resource allocation information, HARQ related parameters, MCS), request for CSI (e.g., aperiodic CQI reports), request for SRS, uplink power control commands for one or more cells, one or more timing information (e.g., TB transmission/reception timing, HARQ feedback timing, etc.), etc. In an example, a DCI may indicate an uplink grant comprising transmission parameters for one or more transport blocks. In an example, a DCI may indicate downlink assignment indicating parameters for receiving one or more transport blocks. In an example, a DCI may be used by base station to initiate a contention-free random access at the wireless device. In an example, the base station may transmit a DCI comprising slot format indicator (SFI) notifying a slot format. In an example, the base station may transmit a DCI comprising pre-emption indication notifying the PRB(s) and/or OFDM symbol(s) where a UE may assume no transmission is intended for the UE. In an example, the base station may transmit a DCI for group power control of PUCCH or PUSCH or SRS. In an example, a DCI may correspond to an RNTI. In an example, the wireless device may obtain an RNTI in response to completing the initial access (e.g., C-RNTI). In an example, the base station may configure an RNTI for the wireless (e.g., CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI). In an example, the wireless device may compute an RNTI (e.g., the wireless device may compute RA-RNTI based on resources used for transmission of a preamble). In an example, an RNTI may have a pre-configured value (e.g., P-RNTI or SI-RNTI). In an example, a wireless device may monitor a group common search space which may be used by base station for transmitting DCIs that are intended for a group of UEs. In an example, a group common DCI may correspond to an RNTI which is commonly configured for a group of UEs. In an example, a wireless device may monitor a UE-specific search space. In an example, a UE specific DCI may correspond to an RNTI configured for the wireless device.

A NR system may support a single beam operation and/or a multi-beam operation. In a multi-beam operation, a base station may perform a downlink beam sweeping to provide coverage for common control channels and/or downlink SS blocks, which may comprise at least a PSS, a SSS, and/or PBCH. A wireless device may measure quality of a beam pair link using one or more RS s. One or more SS blocks, or one or more CSI-RS resources, associated with a CSI-RS resource index (CRI), or one or more DM-RS s of PBCH, may be used as RS for measuring quality of a beam pair link. Quality of a beam pair link may be defined as a reference signal received power (RSRP) value, or a reference signal received quality (RSRQ) value, and/or a CSI value measured on RS resources. The base station may indicate whether an RS resource, used for measuring a beam pair link quality, is quasi-co-located (QCLed) with DM-RS s of a control channel. A RS resource and DM-RS s of a control channel may be called QCLed when a channel characteristics from a transmission on an RS to a wireless device, and that from a transmission on a control channel to a wireless device, are similar or same under a configured criterion. In a multi-beam operation, a wireless device may perform an uplink beam sweeping to access a cell.

In an example, a wireless device may be configured to monitor PDCCH on one or more beam pair links simultaneously depending on a capability of a wireless device. This may increase robustness against beam pair link blocking. A base station may transmit one or more messages to configure a wireless device to monitor PDCCH on one or more beam pair links in different PDCCH OFDM symbols. For example, a base station may transmit higher layer signaling (e.g. RRC signaling) or MAC CE comprising parameters related to the Rx beam setting of a wireless device for monitoring PDCCH on one or more beam pair links. A base station may transmit indication of spatial QCL assumption between an DL RS antenna port(s) (for example, cell-specific CSI-RS, or wireless device-specific CSI-RS, or SS block, or PBCH with or without DM-RS s of PBCH), and DL RS antenna port(s) for demodulation of DL control channel. Signaling for beam indication for a PDCCH may be MAC CE signaling, or RRC signaling, or DCI signaling, or specification-transparent and/or implicit method, and combination of these signaling methods.

For reception of unicast DL data channel, a base station may indicate spatial QCL parameters between DL RS antenna port(s) and DM-RS antenna port(s) of DL data channel. The base station may transmit DCI (e.g. downlink grants) comprising information indicating the RS antenna port(s). The information may indicate RS antenna port(s) which may be QCL-ed with the DM-RS antenna port(s). Different set of DM-RS antenna port(s) for a DL data channel may be indicated as QCL with different set of the RS antenna port(s).

FIG. 9A is an example of beam sweeping in a DL channel. In an RRC INACTIVE state or RRC IDLE state, a wireless device may assume that SS blocks form an SS burst 940, and an SS burst set 950. The SS burst set 950 may have a given periodicity. For example, in a multi-beam operation, a base station 120 may transmit SS blocks in multiple beams, together forming a SS burst 940. One or more SS blocks may be transmitted on one beam. If multiple SS bursts 940 are transmitted with multiple beams, SS bursts together may form SS burst set 950.

A wireless device may further use CSI-RS in the multi-beam operation for estimating a beam quality of a links between a wireless device and a base station. A beam may be associated with a CSI-RS. For example, a wireless device may, based on a RSRP measurement on CSI-RS, report a beam index, as indicated in a CRI for downlink beam selection, and associated with a RSRP value of a beam. A CSI-RS may be transmitted on a CSI-RS resource including at least one of one or more antenna ports, one or more time or frequency radio resources. A CSI-RS resource may be configured in a cell-specific way by common RRC signaling, or in a wireless device-specific way by dedicated RRC signaling, and/or L1/L2 signaling. Multiple wireless devices covered by a cell may measure a cell-specific CSI-RS resource. A dedicated subset of wireless devices covered by a cell may measure a wireless device-specific CSI-RS resource.

A CSI-RS resource may be transmitted periodically, or using aperiodic transmission, or using a multi-shot or semi-persistent transmission. For example, in a periodic transmission in FIG. 9A, a base station 120 may transmit configured CSI-RS resources 940 periodically using a configured periodicity in a time domain. In an aperiodic transmission, a configured CSI-RS resource may be transmitted in a dedicated time slot. In a multi-shot or semi-persistent transmission, a configured CSI-RS resource may be transmitted within a configured period. Beams used for CSI-RS transmission may have different beam width than beams used for SS-blocks transmission.

FIG. 9B is an example of a beam management procedure in an example new radio network. A base station 120 and/or a wireless device 110 may perform a downlink L1/L2 beam management procedure. One or more of the following downlink L1/L2 beam management procedures may be performed within one or more wireless devices 110 and one or more base stations 120. In an example, a P-1 procedure 910 may be used to enable the wireless device 110 to measure one or more Transmission (Tx) beams associated with the base station 120 to support a selection of a first set of Tx beams associated with the base station 120 and a first set of Rx beam(s) associated with a wireless device 110. For beamforming at a base station 120, a base station 120 may sweep a set of different TX beams. For beamforming at a wireless device 110, a wireless device 110 may sweep a set of different Rx beams. In an example, a P-2 procedure 920 may be used to enable a wireless device 110 to measure one or more Tx beams associated with a base station 120 to possibly change a first set of Tx beams associated with a base station 120. A P-2 procedure 920 may be performed on a possibly smaller set of beams for beam refinement than in the P-1 procedure 910. A P-2 procedure 920 may be a special case of a P-1 procedure 910. In an example, a P-3 procedure 930 may be used to enable a wireless device 110 to measure at least one Tx beam associated with a base station 120 to change a first set of Rx beams associated with a wireless device 110.

A wireless device 110 may transmit one or more beam management reports to a base station 120. In one or more beam management reports, a wireless device 110 may indicate some beam pair quality parameters, comprising at least, one or more beam identifications; RSRP; Precoding Matrix Indicator (PMI)/Channel Quality Indicator (CQI)/Rank Indicator (RI) of a subset of configured beams. Based on one or more beam management reports, a base station 120 may transmit to a wireless device 110 a signal indicating that one or more beam pair links are one or more serving beams. A base station 120 may transmit PDCCH and PDSCH for a wireless device 110 using one or more serving beams.

In an example embodiment, new radio network may support a Bandwidth Adaptation (BA). In an example, receive and/or transmit bandwidths configured by an UE employing a BA may not be large. For example, a receive and/or transmit bandwidths may not be as large as a bandwidth of a cell. Receive and/or transmit bandwidths may be adjustable. For example, a UE may change receive and/or transmit bandwidths, e.g., to shrink during period of low activity to save power. For example, a UE may change a location of receive and/or transmit bandwidths in a frequency domain, e.g. to increase scheduling flexibility. For example, a UE may change a subcarrier spacing, e.g. to allow different services.

In an example embodiment, a subset of a total cell bandwidth of a cell may be referred to as a Bandwidth Part (BWP). A base station may configure a UE with one or more BWPs to achieve a BA. For example, a base station may indicate, to a UE, which of the one or more (configured) BWPs is an active BWP.

FIG. 10 is an example diagram of 3 BWPs configured: BWP1 (1010 and 1050) with a width of 40 MHz and subcarrier spacing of 15 kHz; BWP2 (1020 and 1040) with a width of 10 MHz and subcarrier spacing of 15 kHz; BWP3 1030 with a width of 20 MHz and subcarrier spacing of 60 kHz.

In an example, a UE, configured for operation in one or more BWPs of a cell, may be configured by one or more higher layers (e.g. RRC layer) for a cell a set of one or more BWPs (e.g., at most four BWPs) for receptions by the UE (DL BWP set) in a DL bandwidth by at least one parameter DL-BWP and a set of one or more BWPs (e.g., at most four BWPs) for transmissions by a UE (UL BWP set) in an UL bandwidth by at least one parameter UL-BWP for a cell.

To enable BA on the PCell, a base station may configure a UE with one or more UL and DL BWP pairs. To enable BA on SCells (e.g., in case of CA), a base station may configure a UE at least with one or more DL BWPs (e.g., there may be none in an UL).

In an example, an initial active DL BWP may be defined by at least one of a location and number of contiguous PRBs, a subcarrier spacing, or a cyclic prefix, for a control resource set for at least one common search space. For operation on the PCell, one or more higher layer parameters may indicate at least one initial UL BWP for a random access procedure. If a UE is configured with a secondary carrier on a primary cell, the UE may be configured with an initial BWP for random access procedure on a secondary carrier.

In an example, for unpaired spectrum operation, a UE may expect that a center frequency for a DL BWP may be same as a center frequency for a UL BWP.

For example, for a DL BWP or an UL BWP in a set of one or more DL BWPs or one or more UL BWPs, respectively, a base statin may semi-statically configure a UE for a cell with one or more parameters indicating at least one of following: a subcarrier spacing; a cyclic prefix; a number of contiguous PRBs; an index in the set of one or more DL BWPs and/or one or more UL BWPs; a link between a DL BWP and an UL BWP from a set of configured DL BWPs and UL BWPs; a DCI detection to a PDSCH reception timing; a PDSCH reception to a HARQ-ACK transmission timing value; a DCI detection to a PUSCH transmission timing value; an offset of a first PRB of a DL bandwidth or an UL bandwidth, respectively, relative to a first PRB of a bandwidth.

In an example, for a DL BWP in a set of one or more DL BWPs on a PCell, a base station may configure a UE with one or more control resource sets for at least one type of common search space and/or one UE-specific search space. For example, a base station may not configure a UE without a common search space on a PCell, or on a PSCell, in an active DL BWP.

For an UL BWP in a set of one or more UL BWPs, a base station may configure a UE with one or more resource sets for one or more PUCCH transmissions.

In an example, if a DCI comprises a BWP indicator field, a BWP indicator field value may indicate an active DL BWP, from a configured DL BWP set, for one or more DL receptions. If a DCI comprises a BWP indicator field, a BWP indicator field value may indicate an active UL BWP, from a configured UL BWP set, for one or more UL transmissions.

In an example, for a PCell, a base station may semi-statically configure a UE with a default DL BWP among configured DL BWPs. If a UE is not provided a default DL BWP, a default BWP may be an initial active DL BWP.

In an example, a base station may configure a UE with a timer value for a PCell. For example, a UE may start a timer, referred to as BWP inactivity timer, when a UE detects a DCI indicating an active DL BWP, other than a default DL BWP, for a paired spectrum operation or when a UE detects a DCI indicating an active DL BWP or UL BWP, other than a default DL BWP or UL BWP, for an unpaired spectrum operation. The UE may increment the timer by an interval of a first value (e.g., the first value may be 1 millisecond or 0.5 milliseconds) if the UE does not detect a DCI during the interval for a paired spectrum operation or for an unpaired spectrum operation. In an example, the timer may expire when the timer is equal to the timer value. A UE may switch to the default DL BWP from an active DL BWP when the timer expires.

In an example, a base station may semi-statically configure a UE with one or more BWPs. A UE may switch an active BWP from a first BWP to a second BWP in response to receiving a DCI indicating the second BWP as an active BWP and/or in response to an expiry of BWP inactivity timer (for example, the second BWP may be a default BWP). For example, FIG. 10 is an example diagram of 3 BWPs configured, BWP1 (1010 and 1050), BWP2 (1020 and 1040), and BWP3 (1030). BWP2 (1020 and 1040) may be a default BWP. BWP1 (1010) may be an initial active BWP. In an example, a UE may switch an active BWP from BWP1 1010 to BWP2 1020 in response to an expiry of BWP inactivity timer. For example, a UE may switch an active BWP from BWP2 1020 to BWP3 1030 in response to receiving a DCI indicating BWP3 1030 as an active BWP. Switching an active BWP from BWP3 1030 to BWP2 1040 and/or from BWP2 1040 to BWP1 1050 may be in response to receiving a DCI indicating an active BWP and/or in response to an expiry of BWP inactivity timer.

In an example, if a UE is configured for a secondary cell with a default DL BWP among configured DL BWPs and a timer value, UE procedures on a secondary cell may be same as on a primary cell using the timer value for the secondary cell and the default DL BWP for the secondary cell.

In an example, if a base station configures a UE with a first active DL BWP and a first active UL BWP on a secondary cell or carrier, a UE may employ an indicated DL BWP and an indicated UL BWP on a secondary cell as a respective first active DL BWP and first active UL BWP on a secondary cell or carrier.

FIG. 11A and FIG. 11B show packet flows employing a multi connectivity (e.g. dual connectivity, multi connectivity, tight interworking, and/or the like). FIG. 11A is an example diagram of a protocol structure of a wireless device 110 (e.g. UE) with CA and/or multi connectivity as per an aspect of an embodiment. FIG. 11B is an example diagram of a protocol structure of multiple base stations with CA and/or multi connectivity as per an aspect of an embodiment. The multiple base stations may comprise a master node, MN 1130 (e.g. a master node, a master base station, a master gNB, a master eNB, and/or the like) and a secondary node, SN 1150 (e.g. a secondary node, a secondary base station, a secondary gNB, a secondary eNB, and/or the like). A master node 1130 and a secondary node 1150 may co-work to communicate with a wireless device 110.

When multi connectivity is configured for a wireless device 110, the wireless device 110, which may support multiple reception/transmission functions in an RRC connected state, may be configured to utilize radio resources provided by multiple schedulers of a multiple base stations. Multiple base stations may be inter-connected via a non-ideal or ideal backhaul (e.g. Xn interface, X2 interface, and/or the like). A base station involved in multi connectivity for a certain wireless device may perform at least one of two different roles: a base station may either act as a master base station or as a secondary base station. In multi connectivity, a wireless device may be connected to one master base station and one or more secondary base stations. In an example, a master base station (e.g. the MN 1130) may provide a master cell group (MCG) comprising a primary cell and/or one or more secondary cells for a wireless device (e.g. the wireless device 110). A secondary base station (e.g. the SN 1150) may provide a secondary cell group (SCG) comprising a primary secondary cell (PSCell) and/or one or more secondary cells for a wireless device (e.g. the wireless device 110).

In multi connectivity, a radio protocol architecture that a bearer employs may depend on how a bearer is setup. In an example, three different type of bearer setup options may be supported: an MCG bearer, an SCG bearer, and/or a split bearer. A wireless device may receive/transmit packets of an MCG bearer via one or more cells of the MCG, and/or may receive/transmits packets of an SCG bearer via one or more cells of an SCG. Multi-connectivity may also be described as having at least one bearer configured to use radio resources provided by the secondary base station. Multi-connectivity may or may not be configured/implemented in some of the example embodiments.

In an example, a wireless device (e.g. Wireless Device 110) may transmit and/or receive: packets of an MCG bearer via an SDAP layer (e.g. SDAP 1110), a PDCP layer (e.g. NR PDCP 1111), an RLC layer (e.g. MN RLC 1114), and a MAC layer (e.g. MN MAC 1118); packets of a split bearer via an SDAP layer (e.g. SDAP 1110), a PDCP layer (e.g. NR PDCP 1112), one of a master or secondary RLC layer (e.g. MN RLC 1115, SN RLC 1116), and one of a master or secondary MAC layer (e.g. MN MAC 1118, SN MAC 1119); and/or packets of an SCG bearer via an SDAP layer (e.g. SDAP 1110), a PDCP layer (e.g. NR PDCP 1113), an RLC layer (e.g. SN RLC 1117), and a MAC layer (e.g. MN MAC 1119).

In an example, a master base station (e.g. MN 1130) and/or a secondary base station (e.g. SN 1150) may transmit/receive: packets of an MCG bearer via a master or secondary node SDAP layer (e.g. SDAP 1120, SDAP 1140), a master or secondary node PDCP layer (e.g. NR PDCP 1121, NR PDCP 1142), a master node RLC layer (e.g. MN RLC 1124, MN RLC 1125), and a master node MAC layer (e.g. MN MAC 1128); packets of an SCG bearer via a master or secondary node SDAP layer (e.g. SDAP 1120, SDAP 1140), a master or secondary node PDCP layer (e.g. NR PDCP 1122, NR PDCP 1143), a secondary node RLC layer (e.g. SN RLC 1146, SN RLC 1147), and a secondary node MAC layer (e.g. SN MAC 1148); packets of a split bearer via a master or secondary node SDAP layer (e.g. SDAP 1120, SDAP 1140), a master or secondary node PDCP layer (e.g. NR PDCP 1123, NR PDCP 1141), a master or secondary node RLC layer (e.g. MN RLC 1126, SN RLC 1144, SN RLC 1145, MN RLC 1127), and a master or secondary node MAC layer (e.g. MN MAC 1128, SN MAC 1148).

In multi connectivity, a wireless device may configure multiple MAC entities: one MAC entity (e.g. MN MAC 1118) for a master base station, and other MAC entities (e.g. SN MAC 1119) for a secondary base station. In multi-connectivity, a configured set of serving cells for a wireless device may comprise two subsets: an MCG comprising serving cells of a master base station, and SCGs comprising serving cells of a secondary base station. For an SCG, one or more of following configurations may be applied: at least one cell of an SCG has a configured UL CC and at least one cell of a SCG, named as primary secondary cell (PSCell, PCell of SCG, or sometimes called PCell), is configured with PUCCH resources; when an SCG is configured, there may be at least one SCG bearer or one Split bearer; upon detection of a physical layer problem or a random access problem on a PSCell, or a number of NR RLC retransmissions has been reached associated with the SCG, or upon detection of an access problem on a PSCell during a SCG addition or a SCG change: an RRC connection re-establishment procedure may not be triggered, UL transmissions towards cells of an SCG may be stopped, a master base station may be informed by a wireless device of a SCG failure type, for split bearer, a DL data transfer over a master base station may be maintained; an NR RLC acknowledged mode (AM) bearer may be configured for a split bearer; PCell and/or PSCell may not be de-activated; PSCell may be changed with a SCG change procedure (e.g. with security key change and a RACH procedure); and/or a bearer type change between a split bearer and a SCG bearer or simultaneous configuration of a SCG and a split bearer may or may not supported.

With respect to interaction between a master base station and a secondary base stations for multi-connectivity, one or more of the following may be applied: a master base station and/or a secondary base station may maintain RRM measurement configurations of a wireless device; a master base station may (e.g. based on received measurement reports, traffic conditions, and/or bearer types) may decide to request a secondary base station to provide additional resources (e.g. serving cells) for a wireless device; upon receiving a request from a master base station, a secondary base station may create/modify a container that may result in configuration of additional serving cells for a wireless device (or decide that the secondary base station has no resource available to do so); for a UE capability coordination, a master base station may provide (a part of) an AS configuration and UE capabilities to a secondary base station; a master base station and a secondary base station may exchange information about a UE configuration by employing of RRC containers (inter-node messages) carried via Xn messages; a secondary base station may initiate a reconfiguration of the secondary base station existing serving cells (e.g. PUCCH towards the secondary base station); a secondary base station may decide which cell is a PSCell within a SCG; a master base station may or may not change content of RRC configurations provided by a secondary base station; in case of a SCG addition and/or a SCG SCell addition, a master base station may provide recent (or the latest) measurement results for SCG cell(s); a master base station and secondary base stations may receive information of SFN and/or subframe offset of each other from OAM and/or via an Xn interface, (e.g. for a purpose of DRX alignment and/or identification of a measurement gap). In an example, when adding a new SCG SCell, dedicated RRC signaling may be used for sending required system information of a cell as for CA, except for a SFN acquired from a MIB of a PSCell of a SCG.

FIG. 12 is an example diagram of a random access procedure. One or more events may trigger a random access procedure. For example, one or more events may be at least one of following: initial access from RRC_IDLE, RRC connection re-establishment procedure, handover, DL or UL data arrival during RRC_CONNECTED when UL synchronization status is non-synchronized, transition from RRC_Inactive, and/or request for other system information. For example, a PDCCH order, a MAC entity, and/or a beam failure indication may initiate a random access procedure.

In an example embodiment, a random access procedure may be at least one of a contention based random access procedure and a contention free random access procedure. For example, a contention based random access procedure may comprise, one or more Msg 1 1220 transmissions, one or more Msg2 1230 transmissions, one or more Msg3 1240 transmissions, and contention resolution 1250. For example, a contention free random access procedure may comprise one or more Msg 1 1220 transmissions and one or more Msg2 1230 transmissions.

In an example, a base station may transmit (e.g., unicast, multicast, or broadcast), to a UE, a RACH configuration 1210 via one or more beams. The RACH configuration 1210 may comprise one or more parameters indicating at least one of following: available set of PRACH resources for a transmission of a random access preamble, initial preamble power (e.g., random access preamble initial received target power), an RSRP threshold for a selection of a SS block and corresponding PRACH resource, a power-ramping factor (e.g., random access preamble power ramping step), random access preamble index, a maximum number of preamble transmission, preamble group A and group B, a threshold (e.g., message size) to determine the groups of random access preambles, a set of one or more random access preambles for system information request and corresponding PRACH resource(s), if any, a set of one or more random access preambles for beam failure recovery request and corresponding PRACH resource(s), if any, a time window to monitor RA response(s), a time window to monitor response(s) on beam failure recovery request, and/or a contention resolution timer.

In an example, the Msg 1 1220 may be one or more transmissions of a random access preamble. For a contention based random access procedure, a UE may select a SS block with a RSRP above the RSRP threshold. If random access preambles group B exists, a UE may select one or more random access preambles from a group A or a group B depending on a potential Msg 3 1240 size. If a random access preambles group B does not exist, a UE may select the one or more random access preambles from a group A. A UE may select a random access preamble index randomly (e.g. with equal probability or a normal distribution) from one or more random access preambles associated with a selected group. If a base station semi-statically configures a UE with an association between random access preambles and SS blocks, the UE may select a random access preamble index randomly with equal probability from one or more random access preambles associated with a selected SS block and a selected group.

For example, a UE may initiate a contention free random access procedure based on a beam failure indication from a lower layer. For example, a base station may semi-statically configure a UE with one or more contention free PRACH resources for beam failure recovery request associated with at least one of SS blocks and/or CSI-RS s. If at least one of SS blocks with a RSRP above a first RSRP threshold amongst associated SS blocks or at least one of CSI-RSs with a RSRP above a second RSRP threshold amongst associated CSI-RSs is available, a UE may select a random access preamble index corresponding to a selected SS block or CSI-RS from a set of one or more random access preambles for beam failure recovery request.

For example, a UE may receive, from a base station, a random access preamble index via PDCCH or RRC for a contention free random access procedure. If a base station does not configure a UE with at least one contention free PRACH resource associated with SS blocks or CSI-RS, the UE may select a random access preamble index. If a base station configures a UE with one or more contention free PRACH resources associated with SS blocks and at least one SS block with a RSRP above a first RSRP threshold amongst associated SS blocks is available, the UE may select the at least one SS block and select a random access preamble corresponding to the at least one SS block. If a base station configures a UE with one or more contention free PRACH resources associated with CSI-RSs and at least one CSI-RS with a RSRP above a second RSPR threshold amongst the associated CSI-RS s is available, the UE may select the at least one CSI-RS and select a random access preamble corresponding to the at least one CSI-RS.

A UE may perform one or more Msg1 1220 transmissions by transmitting the selected random access preamble. For example, if a UE selects an SS block and is configured with an association between one or more PRACH occasions and one or more SS blocks, the UE may determine an PRACH occasion from one or more PRACH occasions corresponding to a selected SS block. For example, if a UE selects a CSI-RS and is configured with an association between one or more PRACH occasions and one or more CSI-RS s, the UE may determine a PRACH occasion from one or more PRACH occasions corresponding to a selected CSI-RS. A UE may transmit, to a base station, a selected random access preamble via a selected PRACH occasions. A UE may determine a transmit power for a transmission of a selected random access preamble at least based on an initial preamble power and a power-ramping factor. A UE may determine a RA-RNTI associated with a selected PRACH occasions in which a selected random access preamble is transmitted. For example, a UE may not determine a RA-RNTI for a beam failure recovery request. A UE may determine an RA-RNTI at least based on an index of a first OFDM symbol and an index of a first slot of a selected PRACH occasions, and/or an uplink carrier index for a transmission of Msg1 1220.

In an example, a UE may receive, from a base station, a random access response, Msg 2 1230. A UE may start a time window (e.g., ra-Response Window) to monitor a random access response. For beam failure recovery request, a base station may configure a UE with a different time window (e.g., bfr-Response Window) to monitor response on beam failure recovery request. For example, a UE may start a time window (e.g., ra-ResponseWindow or bfr-Response Window) at a start of a first PDCCH occasion after a fixed duration of one or more symbols from an end of a preamble transmission. If a UE transmits multiple preambles, the UE may start a time window at a start of a first PDCCH occasion after a fixed duration of one or more symbols from an end of a first preamble transmission. A UE may monitor a PDCCH of a cell for at least one random access response identified by a RA-RNTI or for at least one response to beam failure recovery request identified by a C-RNTI while a timer for a time window is running.

In an example, a UE may consider a reception of random access response successful if at least one random access response comprises a random access preamble identifier corresponding to a random access preamble transmitted by the UE. A UE may consider the contention free random access procedure successfully completed if a reception of random access response is successful. If a contention free random access procedure is triggered for a beam failure recovery request, a UE may consider a contention free random access procedure successfully complete if a PDCCH transmission is addressed to a C-RNTI. In an example, if at least one random access response comprises a random access preamble identifier, a UE may consider the random access procedure successfully completed and may indicate a reception of an acknowledgement for a system information request to upper layers. If a UE has signaled multiple preamble transmissions, the UE may stop transmitting remaining preambles (if any) in response to a successful reception of a corresponding random access response.

In an example, a UE may perform one or more Msg 3 1240 transmissions in response to a successful reception of random access response (e.g., for a contention based random access procedure). A UE may adjust an uplink transmission timing based on a timing advanced command indicated by a random access response and may transmit one or more transport blocks based on an uplink grant indicated by a random access response. Subcarrier spacing for PUSCH transmission for Msg 3 1240 may be provided by at least one higher layer (e.g. RRC) parameter. A UE may transmit a random access preamble via PRACH and Msg 3 1240 via PUSCH on a same cell. A base station may indicate an UL BWP for a PUSCH transmission of Msg 3 1240 via system information block. A UE may employ HARQ for a retransmission of Msg 3 1240.

In an example, multiple UEs may perform Msg 1 1220 by transmitting a same preamble to a base station and receive, from the base station, a same random access response comprising an identity (e.g., TC-RNTI). Contention resolution 1250 may ensure that a UE does not incorrectly use an identity of another UE. For example, contention resolution 1250 may be based on C-RNTI on PDCCH or a UE contention resolution identity on DL-SCH. For example, if a base station assigns a C-RNTI to a UE, the UE may perform contention resolution 1250 based on a reception of a PDCCH transmission that is addressed to the C-RNTI. In response to detection of a C-RNTI on a PDCCH, a UE may consider contention resolution 1250 successful and may consider a random access procedure successfully completed. If a UE has no valid C-RNTI, a contention resolution may be addressed by employing a TC-RNTI. For example, if a MAC PDU is successfully decoded and a MAC PDU comprises a UE contention resolution identity MAC CE that matches the CCCH SDU transmitted in Msg 3 1250, a UE may consider the contention resolution 1250 successful and may consider the random access procedure successfully completed.

FIG. 13 is an example structure for MAC entities as per an aspect of an embodiment. In an example, a wireless device may be configured to operate in a multi-connectivity mode. A wireless device in RRC_CONNECTED with multiple RX/TX may be configured to utilize radio resources provided by multiple schedulers located in a plurality of base stations. The plurality of base stations may be connected via a non-ideal or ideal backhaul over the Xn interface. In an example, a base station in a plurality of base stations may act as a master base station or as a secondary base station. A wireless device may be connected to one master base station and one or more secondary base stations. A wireless device may be configured with multiple MAC entities, e.g. one MAC entity for master base station, and one or more other MAC entities for secondary base station(s). In an example, a configured set of serving cells for a wireless device may comprise two subsets: an MCG comprising serving cells of a master base station, and one or more SCGs comprising serving cells of a secondary base station(s). FIG. 13 illustrates an example structure for MAC entities when MCG and SCG are configured for a wireless device.

In an example, at least one cell in a SCG may have a configured UL CC, wherein a cell of at least one cell may be called PSCell or PCell of SCG, or sometimes may be simply called PCell. A PSCell may be configured with PUCCH resources. In an example, when a SCG is configured, there may be at least one SCG bearer or one split bearer. In an example, upon detection of a physical layer problem or a random access problem on a PSCell, or upon reaching a number of RLC retransmissions associated with the SCG, or upon detection of an access problem on a PSCell during a SCG addition or a SCG change: an RRC connection re-establishment procedure may not be triggered, UL transmissions towards cells of an SCG may be stopped, a master base station may be informed by a UE of a SCG failure type and DL data transfer over a master base station may be maintained.

In an example, a MAC sublayer may provide services such as data transfer and radio resource allocation to upper layers (e.g. 1310 or 1320). A MAC sublayer may comprise a plurality of MAC entities (e.g. 1350 and 1360). A MAC sublayer may provide data transfer services on logical channels. To accommodate different kinds of data transfer services, multiple types of logical channels may be defined. A logical channel may support transfer of a particular type of information. A logical channel type may be defined by what type of information (e.g., control or data) is transferred. For example, BCCH, PCCH, CCCH and DCCH may be control channels and DTCH may be a traffic channel. In an example, a first MAC entity (e.g. 1310) may provide services on PCCH, BCCH, CCCH, DCCH, DTCH and MAC control elements. In an example, a second MAC entity (e.g. 1320) may provide services on BCCH, DCCH, DTCH and MAC control elements.

A MAC sublayer may expect from a physical layer (e.g. 1330 or 1340) services such as data transfer services, signaling of HARQ feedback, signaling of scheduling request or measurements (e.g. CQI). In an example, in dual connectivity, two MAC entities may be configured for a wireless device: one for MCG and one for SCG. A MAC entity of wireless device may handle a plurality of transport channels. In an example, a first MAC entity may handle first transport channels comprising a PCCH of MCG, a first BCH of MCG, one or more first DL-SCHs of MCG, one or more first UL-SCHs of MCG and one or more first RACHs of MCG. In an example, a second MAC entity may handle second transport channels comprising a second BCH of SCG, one or more second DL-SCHs of SCG, one or more second UL-SCHs of SCG and one or more second RACHs of SCG.

In an example, if a MAC entity is configured with one or more SCells, there may be multiple DL-SCHs and there may be multiple UL-SCHs as well as multiple RACHs per MAC entity. In an example, there may be one DL-SCH and UL-SCH on a SpCell. In an example, there may be one DL-SCH, zero or one UL-SCH and zero or one RACH for an SCell. A DL-SCH may support receptions using different numerologies and/or TTI duration within a MAC entity. A UL-SCH may also support transmissions using different numerologies and/or TTI duration within the MAC entity.

In an example, a MAC sublayer may support different functions and may control these functions with a control (e.g. 1355 or 1365) element. Functions performed by a MAC entity may comprise mapping between logical channels and transport channels (e.g., in uplink or downlink), multiplexing (e.g. 1352 or 1362) of MAC SDUs from one or different logical channels onto transport blocks (TB) to be delivered to the physical layer on transport channels (e.g., in uplink), demultiplexing (e.g. 1352 or 1362) of MAC SDUs to one or different logical channels from transport blocks (TB) delivered from the physical layer on transport channels (e.g., in downlink), scheduling information reporting (e.g., in uplink), error correction through HARQ in uplink or downlink (e.g. 1363), and logical channel prioritization in uplink (e.g. 1351 or 1361). A MAC entity may handle a random access process (e.g. 1354 or 1364).

FIG. 14 is an example diagram of a RAN architecture comprising one or more base stations. In an example, a protocol stack (e.g. RRC, SDAP, PDCP, RLC, MAC, and PHY) may be supported at a node. A base station (e.g. 120A or 120B) may comprise a base station central unit (CU) (e.g. gNB-CU 1420A or 1420B) and at least one base station distributed unit (DU) (e.g. gNB-DU 1430A, 1430B, 1430C, or 1430D) if a functional split is configured. Upper protocol layers of a base station may be located in a base station CU, and lower layers of the base station may be located in the base station DUs. An F1 interface (e.g. CU-DU interface) connecting a base station CU and base station DUs may be an ideal or non-ideal backhaul. F1-C may provide a control plane connection over an F1 interface, and F1-U may provide a user plane connection over the F1 interface. In an example, an Xn interface may be configured between base station CUs.

In an example, a base station CU may comprise an RRC function, an SDAP layer, and a PDCP layer, and base station DUs may comprise an RLC layer, a MAC layer, and a PHY layer. In an example, various functional split options between a base station CU and base station DUs may be possible by locating different combinations of upper protocol layers (RAN functions) in a base station CU and different combinations of lower protocol layers (RAN functions) in base station DUs. A functional split may support flexibility to move protocol layers between a base station CU and base station DUs depending on service requirements and/or network environments.

In an example, functional split options may be configured per base station, per base station CU, per base station DU, per UE, per bearer, per slice, or with other granularities. In per base station CU split, a base station CU may have a fixed split option, and base station DUs may be configured to match a split option of a base station CU. In per base station DU split, a base station DU may be configured with a different split option, and a base station CU may provide different split options for different base station DUs. In per UE split, a base station (base station CU and at least one base station DUs) may provide different split options for different wireless devices. In per bearer split, different split options may be utilized for different bearers. In per slice splice, different split options may be applied for different slices.

FIG. 15 is an example diagram showing RRC state transitions of a wireless device. In an example, a wireless device may be in at least one RRC state among an RRC connected state (e.g. RRC Connected 1530, RRC_Connected), an RRC idle state (e.g. RRC Idle 1510, RRC_Idle), and/or an RRC inactive state (e.g. RRC Inactive 1520, RRC_Inactive). In an example, in an RRC connected state, a wireless device may have at least one RRC connection with at least one base station (e.g. gNB and/or eNB), which may have a UE context of the wireless device. A UE context (e.g. a wireless device context) may comprise at least one of an access stratum context, one or more radio link configuration parameters, bearer (e.g. data radio bearer (DRB), signaling radio bearer (SRB), logical channel, QoS flow, PDU session, and/or the like) configuration information, security information, PHY/MAC/RLC/PDCP/SDAP layer configuration information, and/or the like configuration information for a wireless device. In an example, in an RRC idle state, a wireless device may not have an RRC connection with a base station, and a UE context of a wireless device may not be stored in a base station. In an example, in an RRC inactive state, a wireless device may not have an RRC connection with a base station. A UE context of a wireless device may be stored in a base station, which may be called as an anchor base station (e.g. last serving base station).

In an example, a wireless device may transition a UE RRC state between an RRC idle state and an RRC connected state in both ways (e.g. connection release 1540 or connection establishment 1550; or connection reestablishment) and/or between an RRC inactive state and an RRC connected state in both ways (e.g. connection inactivation 1570 or connection resume 1580). In an example, a wireless device may transition its RRC state from an RRC inactive state to an RRC idle state (e.g. connection release 1560).

In an example, an anchor base station may be a base station that may keep a UE context (a wireless device context) of a wireless device at least during a time period that a wireless device stays in a RAN notification area (RNA) of an anchor base station, and/or that a wireless device stays in an RRC inactive state. In an example, an anchor base station may be a base station that a wireless device in an RRC inactive state was lastly connected to in a latest RRC connected state or that a wireless device lastly performed an RNA update procedure in. In an example, an RNA may comprise one or more cells operated by one or more base stations. In an example, a base station may belong to one or more RNAs. In an example, a cell may belong to one or more RNAs.

In an example, a wireless device may transition a UE RRC state from an RRC connected state to an RRC inactive state in a base station. A wireless device may receive RNA information from the base station. RNA information may comprise at least one of an RNA identifier, one or more cell identifiers of one or more cells of an RNA, a base station identifier, an IP address of the base station, an AS context identifier of the wireless device, a resume identifier, and/or the like.

In an example, an anchor base station may broadcast a message (e.g. RAN paging message) to base stations of an RNA to reach to a wireless device in an RRC inactive state, and/or the base stations receiving the message from the anchor base station may broadcast and/or multicast another message (e.g. paging message) to wireless devices in their coverage area, cell coverage area, and/or beam coverage area associated with the RNA through an air interface.

In an example, when a wireless device in an RRC inactive state moves into a new RNA, the wireless device may perform an RNA update (RNAU) procedure, which may comprise a random access procedure by the wireless device and/or a UE context retrieve procedure. A UE context retrieve may comprise: receiving, by a base station from a wireless device, a random access preamble; and fetching, by a base station, a UE context of the wireless device from an old anchor base station. Fetching may comprise: sending a retrieve UE context request message comprising a resume identifier to the old anchor base station and receiving a retrieve UE context response message comprising the UE context of the wireless device from the old anchor base station.

In an example embodiment, a wireless device in an RRC inactive state may select a cell to camp on based on at least a on measurement results for one or more cells, a cell where a wireless device may monitor an RNA paging message and/or a core network paging message from a base station. In an example, a wireless device in an RRC inactive state may select a cell to perform a random access procedure to resume an RRC connection and/or to transmit one or more packets to a base station (e.g. to a network). In an example, if a cell selected belongs to a different RNA from an RNA for a wireless device in an RRC inactive state, the wireless device may initiate a random access procedure to perform an RNA update procedure. In an example, if a wireless device in an RRC inactive state has one or more packets, in a buffer, to transmit to a network, the wireless device may initiate a random access procedure to transmit one or more packets to a base station of a cell that the wireless device selects. A random access procedure may be performed with two messages (e.g. 2 stage random access) and/or four messages (e.g. 4 stage random access) between the wireless device and the base station.

In an example embodiment, a base station receiving one or more uplink packets from a wireless device in an RRC inactive state may fetch a UE context of a wireless device by transmitting a retrieve UE context request message for the wireless device to an anchor base station of the wireless device based on at least one of an AS context identifier, an RNA identifier, a base station identifier, a resume identifier, and/or a cell identifier received from the wireless device. In response to fetching a UE context, a base station may transmit a path switch request for a wireless device to a core network entity (e.g. AMF, MME, and/or the like). A core network entity may update a downlink tunnel endpoint identifier for one or more bearers established for the wireless device between a user plane core network entity (e.g. UPF, S-GW, and/or the like) and a RAN node (e.g. the base station), e.g. changing a downlink tunnel endpoint identifier from an address of the anchor base station to an address of the base station.

A gNB may communicate with a wireless device via a wireless network employing one or more new radio technologies. The one or more radio technologies may comprise at least one of: multiple technologies related to physical layer; multiple technologies related to medium access control layer; and/or multiple technologies related to radio resource control layer. Example embodiments of enhancing the one or more radio technologies may improve performance of a wireless network. Example embodiments may increase the system throughput, or data rate of transmission. Example embodiments may reduce battery consumption of a wireless device. Example embodiments may improve latency of data transmission between a gNB and a wireless device. Example embodiments may improve network coverage of a wireless network. Example embodiments may improve transmission efficiency of a wireless network.

Random access (RA) procedures may be used to establish communications between a wireless device and a base station in a cell. A four-step RA procedure in FIG. 12 may have an associated latency, e.g., which may be a minimum of fourteen transmission time intervals (TTI). As an example, 3GPP TR 38.804 v14.0.0 indicates a minimum latency of fourteen TTIs comprising, e.g., 3 TTIs after a message from step 1 1220 of a four-step RA procedure, 1 TTI for a message from step 2 1230 of a four-step RA procedure, 5 TTIs after the message from step 2, 1 TTI for a message from step 3 1240 of a four-step RA procedure, 3 TTIs after the message from step 3, and 1 TTI for a message from step 4 1250 of a four-step procedure (e.g., 3+1+5+1+3+1=14). Reducing the number of steps in an RA procedure may reduce latency. By using parallel transmissions, a four-step RA procedure may be reduced to a two-step RA procedure. A two-step RA procedure may have an associated latency, e.g., which may be a minimum of four TTIs and which may be less than an associated latency for a four-step RA procedure. As an example, 3GPP TR 38.804 v14.0.0 indicates a minimum latency of four TTIs comprising, e.g., 3 TTIs after a message from step 1 of a two-step RA procedure and 1 TTI for a message from step 2 of a two-step RA procedure.

FIG. 16 is an example of a two-step RA procedure that may comprise an uplink (UL) transmission of a two-step Msg1 1620 that may comprise a random access preamble (RAP) transmission 1630 and one or more transport blocks transmission 1640, followed by a downlink (DL) transmission of a two-step Msg2 1650 that may comprise a response, e.g., random access response (RAR), corresponding to the uplink transmission. The response may comprise contention resolution information.

A base station may transmit one or more RRC messages to configure a wireless device with one or more parameters of two step RACH configuration 1610. The one or more RRC messages may broadcast or multicast to one or more wireless devices. The one or more RRC messages may be wireless device-specific messages, e.g., a dedicated RRC message transmitted to a wireless device with RRC INACTIVE 1520 or RRC CONNECTED 1530. The one or more RRC messages may comprise parameters required for transmitting a two-step Msg 1 1620. For example, the parameter may indicate at least one of following: PRACH resource allocation, preamble format, SSB information (e.g., total number of SSBs, downlink resource allocation of SSB transmission, transmission power of SSB transmission, and/or other information), and uplink radio resources for one or more transport block transmissions.

In the UL transmission of a two-step RA procedure, a wireless device may transmit, via a cell and to a base station, a RAP for UL time alignment and/or one or more transport blocks (e.g., delay-sensitive data, wireless device ID, security information, device information such as IMSI, and/or other information). In the DL transmission of the two-step RA procedure, a base station may transmit a two-step Msg2 1650 (e.g., an RAR) that may comprise at least one of following: a timing advance command indicating the TA value, a power control command, an UL grant (e.g., radio resource assignment, and/or MCS), a wireless device ID for contention resolution, an RNTI (e.g., C-RNTI or TC-RNTI), and/or other information. The two-step Msg2 1650 (e.g., an RAR) may comprise a preamble identifier corresponding to the preamble 1630, a positive or negative acknowledgement of a reception of the one or more transport blocks 1640, and/or an indication of a successful decoding of the one or more transport blocks 1640. A two-step RA procedure may reduce RA latency compared with a four-step RA procedure, e.g., by integrating a random access preamble transmission (e.g., a process to obtain a timing advance value) with one or more transport block transmissions.

In the UL transmission of a two-step RA procedure, a wireless device may transmit, via a cell and to a base station, an RAP in parallel with one or more TB s. The wireless device may acquire one or more configuration parameters for the UL transmission before the wireless device starts a two-step RA procedure, e.g., at step 1610 in FIG. 16. For example, the one or more configuration parameters may indicate at least one of following: PRACH resource allocation, preamble format, SSB information (e.g., a number of transmitting SSBs, downlink resource allocation of SSB transmissions, transmission power of SSB transmission, and/or other information), uplink radio resources (in terms of time, frequency, code/sequence/signature) for one or more transport block transmissions, and power control parameters of one or more TB transmissions (e.g., cell and/or UE specific power adjustments used for calculating received target power, inter-cell interference control parameter that may be used as a scaling factor of pathloss measurement, reference signal power to calculate for pathloss measurement, and/or one or more margins).

There may be one or more ways for a wireless device to generate an RAP. For example, a two-step RACH configuration may comprise an RAP generating parameters (e.g., a root sequence) that may be employed by the wireless device to generate an RAP. The wireless device may employ the RAP generating parameters to generate one or more candidate preambles and may randomly select one of the candidate preambles as the RAP. The RAP generating parameters may be SSB specific and/or cell-specific. For example, a RAP generating parameters for a first SSB may be different from or the same to a RAP generating parameters for a second SSB. For example, a base station may transmit a control message (e.g., RRC message for a handover, and/or a PDCCH order for a secondary cell addition) that comprise a preamble index of an RAP dedicated to a wireless device to initiate a two-step RA procedure. The one or more candidate preambles may be organized into groups that may indicate an amount of data for transmission. In an example, the amount of data may indicate one or more transport blocks that remain in the buffer. Each of the groups may be associated with a range of data size. For example, a first group of the groups may comprise RAPs indicated for small data transmissions, and a second group may comprise RAPs indicated for larger data transmissions. A base station may transmit an RRC message comprising one or more thresholds with which a wireless device may determine a group of RAP by comparing the one or more thresholds and the amount of data. By transmitting an RAP from a specific group of RAPs, the wireless device may be able to indicate a size of data it may have for transmission.

In a two-step RA procedure, a wireless device may transmit the RAP via a RACH resource indicated by a two-step RACH configuration. The wireless device may transmit one or more TBs via an UL radio resource indicated by a two-step RACH configuration. The transmission of the RAP may be overlapped in time (partially or entirely) with the transmission of the one or more TBs. The two-step RACH configuration may indicate a portion of overlapping of radio resources between the RAP and one or more TB transmissions. The two-step RACH configuration may indicate one or more UL radio resources associated with one or more RAPs (or RAP groups) and/or the RACH resource. For example, based on a selection of an RAP, an RAP group, and/or an RACH resource, a wireless device may determine at least one UL radio resource where the wireless device transmits one or more TBs as a part of a two-step RACH procedure. The one or more UL radio resources may be indicated based on a frame structure in FIG. 6, and/or OFDM radio structure in FIG. 8, e.g., with respect to an SFN (SNR=0), slot number, and/or OFDM symbol number for a time domain radio resource, and/or with respect to a subcarrier number, a number of resource elements, a number of resource blocks, RBG number, and/or frequency index for a frequency domain radio resource. For example, the one or more UL radio resources may be indicated based on a time offset and/or a frequency offset with respect to one or more RACH resources of a selected RAP. The UL transmissions may occur, e.g., in the same subframe (or slot/mini-slot), in consecutive subframes (or slot/mini-slot), or in the same burst.

For example, a PRACH resource and one or more associated UL radio resources for a two-step Msg1 may be allocated with a time offset and/or frequency offset, e.g., provided by RRC messages (as a part of RACH config.) and/or predefined (e.g., as a mapping table). FIG. 17A, FIG. 17B, and FIG. 17C are examples of radio resource allocations of a PRACH resource and one or more associated UL radio resources based on a time offset, a frequency offset, and a combination of a time offset and a frequency offset, respectively. The examples in FIG. 17A, FIG. 17B, and FIG. 17C may be a case of a PRACH resource and a UL radio resource where a single SSB transmission is configured. The examples may be a case of a PRACH resource and a UL radio resource associated with a first SSB transmission of one or more SSB transmissions.

A base station may acquire a UL transmission timing by detecting an RAP transmitted PRACH resource based on the time offset and/or the frequency offset. A base station may detect and/or decode one or more transport blocks transmitted via one or more associated UL radio resources based on the UL transmission timing acquired from the RAP detection. For example, a base station may transmit one or more SSBs, and each of the one or more SSBs may have one or more associated PRACH and UL radio resources provided by a two-step RACH configuration. A wireless device may measure one or more SSBs, and based on measured received signal strength (or based on other selection rule), may select at least one SSB. The wireless device may respectively transmit an RAP and one or more transport blocks via PRACH associated with the at least one SSB, and via UL radio resources associated with the PRACH and/or the at least one SSB.

In an example, a base station may employ the RAP to adjust UL transmission time for a cell and/or to aid in channel estimation for one or more TBs. A portion of the UL transmission for one or more TBs in a two-step RACH procedure may comprise, e.g., a wireless device ID, a C-RNTI, a service request such as buffer state reporting (e.g., a buffer status report) (BSR), one or more user data packets, and/or other information. A wireless device in an RRC CONNECTED state may use a C-RNTI as an identifier of the wireless device (e.g., a wireless device ID). A wireless device in an RRC INACTIVE state may use a C-RNTI (if available), a resume ID, or a short MAC-ID as an identifier of the wireless device. A wireless device in an RRC IDLE state may use a C-RNTI (if available), a resume ID, a short MACID, an IMSI (International Mobile Subscriber Identifier), a T-IMSI (Temporary-IMSI), and/or a random number as an identifier of the wireless device.

In a two-step RACH procedure, the UL transmission may comprise one or more TBs that may be transmitted in one or more ways. One or more transport blocks may be multiplexed with an RAP transmission in time and/or frequency domains. A base station may configure one or more resources reserved for the UL transmission that may be indicated to a wireless device before the UL transmission. If a wireless device transmits one or more TBs in a two-step Msg 1 1620 of a two-step RA procedure, a base station may transmit in a two-step Msg2 1650 (e.g., an RAR) that may comprise a contention resolution message and/or an acknowledgement (ACK or NACK) message of the one or more TBs. A wireless device may transmit one or more second TBs after the reception of an RAR. The wireless device may transmit an indicator, such as buffer state reporting, in a two-step Msg 1 1620 of a two-step RA procedure. The indicator may indicate to a base station an amount of data the wireless device to transmit and/or an amount of data remains in a buffer. The base station may determine a UL grant based on the indicator. The base station may transmit the UL grant to the wireless device via an RAR.

In a two-step/RA procedure, a wireless device may receive two separate responses; a first response for RAP transmission; and a second response for one or more TB transmission. A wireless device may monitor a common search space to detect the first response with a random access RNTI generated based on time and frequency indices of PRACH resource where the wireless device transmits an RAP. A wireless device may monitor a common search space and/or a wireless device specific search space to detect the second response. To detect the second response, the wireless device may employ a C-RNTI (e.g., if configured) or a random access RNTI generated based on time and frequency indices of PRACH resource where the wireless device transmits an RAP. The wireless device specific search space may be predefined and/or configured by an RRC message.

One or more events may trigger a two-step random access procedure. For example, one or more events may be at least one of following: initial access from RRC IDLE, RRC connection re-establishment procedure, handover, DL or UL data arrival during RRC CONNECTED when UL synchronization status is non-synchronized, transition from RRC Inactive, beam failure recovery procedure, and/or request for other system information. For example, a PDCCH order, a MAC entity, and/or a beam failure indication may initiate a random access procedure.

A two-step RA procedure may be initiated based on one or more case-based procedures, services, or radio conditions. For example, if a cell is small such that there may be no need for a TA, a base station in the cell may configure one or more wireless devices under its coverage to use a two-step RA procedure. A wireless device may acquire the configuration, via one or more RRC messages (e.g., system information blocks, multicast and/or unicast RRC signaling), and/or via LI control signaling (e.g., PDCCH order) used to initiate a two-step RA procedure.

For example, in a macro coverage area, a wireless device may have a stored and/or persisted TA value, e.g., a stationary or near stationary wireless device such as a sensor-type wireless device. In this case a two-step RA procedure may be initiated. A base station having macro coverage may use broadcasting and/or dedicated signaling to configure a two-step RA procedure with one or more wireless devices having stored and/or persisted TA values under the coverage.

A wireless device in an RRC connected state may perform a two-step RA procedure. For example, the two -step RA procedure may be initiated when a wireless device performs a handover (e.g., network-initiated handover), and/or when the wireless device requires or requests a UL grant for a transmission of delay-sensitive data and there are no physical-layer uplink control channel resources available to transmit a scheduling request. A wireless device in an RRC INACTIVE state may perform a two-step RA procedure, e.g., for a small data transmission while remaining in the RRC INACTIVE state or for resuming a connection. A wireless device may initiate a two-step RA procedure, for example, for initial access such as establishing a radio link, re-establishment of a radio link, handover, establishment of UL synchronization, and/or a scheduling request when there is no UL grant.

The following description presents one or more examples of a RACH procedure. The procedures and/or parameters described in the following may not be limited to a specific RA procedure. The procedures and/or parameters described in the following may be applied for a four-step RA procedure and/or a two-step RA procedure. For example, a RA procedure may refer to a four-step RA procedure and/or a two-step RA procedure in the following description.

In an example, a base station may transmit, to a wireless device, one or more messages indicating random access parameters of a four-step random access procedure in FIG. 12 and/or a two-step random access procedure in FIG. 16. For example, the one or more messages may be broadcast RRC message, wireless device specific RRC message, and/or combination thereof. For example, the one or more message may comprise at least one of RACH-ConfigCommon, RACH-ConfigGeneric, and RACH-ConfigDedicated. For example, for a contention based (four-step and/or a two-step) random access procedure, a wireless device may receive, from a base station, at least RACH-ConfigCommon and RACH-ConfigGeneric. For example, for a contention free (four-step and/or a two-step) random access procedure, a wireless device may receive, from a base station, at least RACH-ConfigDedicated.

For example, a random access procedure may be initiated in one or more ways based at least on one of RACH-ConfigCommon, RACH-ConfigGeneric, and RACH-ConfigDedicated. For example, a random access procedure may be initiated by a PDCCH order transmitted by a base station, by the MAC entity of a wireless device, or by RRC. There may be one random access procedure ongoing at any point in time in a MAC entity. A random access procedure on a cell (e.g., an SCell) may be initiated by a PDCCH order with ra-PreambleIndex different from a first index (e.g., that may be predefined or configured e.g., 0b000000). For example, if the MAC entity of a wireless device receives a request for a random access procedure while another is already ongoing in the MAC entity, a wireless device may continue with the ongoing procedure or start with the new procedure (e.g. for SI request).

An example random access common configuration (e.g., RACH-ConfigCommon) may be below:

RACH-ConfigCommon ::= SEQUENCE {  rach-ConfigGeneric RACH-ConfigGeneric,  totalNumberOfRA-Preambles INTEGER (1..63) OPTIONAL, -- Need S  ssb-perRACH-OccasionAndCB-PreamblesPerSSB CHOICE {   oneEighth ENUMERATED  {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64},   oneFourth ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64},   oneHalf ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64},   one ENUMERATED n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64},   two ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32},   four INTEGER (1..16),   eight INTEGER (1..8),   sixteen INTEGER (1..4)  } OPTIONAL,-- Need M  groupBconfigured SEQUENCE {   ra-Msg3SizeGroupA ENUMERATED { b56, b144, b208, b256, b282, b480,  b640, b800, b1000, spare7, spare6, spare5, spare4, spare3, spare2, spare1},   messagePowerOffsetGroupB ENUMERATED { minusinfinity, dB0, dB5, dB8, dB10, dB12, dB15, dB18},   numberOfRA-PreamblesGroupA  INTEGER (1..64)  } OPTIONAL,-- Need R  ra-ContentionResolutionTimer  ENUMERATED { sf8, sf16, sf24, sf32, sf40, sf48, sf56, sf64},  rsrp-ThresholdSSB  RSRP-Range OPTIONAL, -- Need R  rsrp-ThresholdSSB-SUL  RSRP-Range OPTIONAL, -- Cond SUL  prach-RootSequenceIndex  CHOICE {   l839 INTEGER (0..837),   l139 INTEGER (0..137)  },  msg1-SubcarrierSpacing SubcarrierSpacing OPTIONAL, --Need S  restrictedSetConfig  ENUMERATED {unrestrictedSet, restrictedSetTypeA, restrictedSetTypeB},  msg3-transformPrecoding ENUMERATED {enabled} OPTIONAL, -- Need R  ... }

For example, messagePowerOffsetGroupB may indicate a threshold for preamble selection. The value of messagePowerOffsetGroupB may be in dB. For example, minusinfinity in RACH-ConfigCommon may corresponds to -infinity. The value dB0 may correspond to 0 dB, dB5 may correspond to 5 dB and so on. msg1-SubcarrierSpacing in RACH-ConfigCommon may indicate a subcarrier spacing of PRACH. One or more values, e.g., 15 or 30 kHz (<6 GHz), 60 or 120 kHz (>6 GHz) may be applicable. There may be a layer 1 parameter (e.g., ‘prach-Msg 1 SubcarrierSpacing) corresponding to msg1-SubcarrierSpacing. A wireless device may apply the SCS as derived from the prach-ConfigurationIndex in RACH-ConfigGeneric, for example, if this parameter is absent. A base station may employ msg3-transformPrecoding to indicate to a wireless device whether transform precoding is enabled for data transmission (e.g., Msg3 in a four-step RA procedure and/or one or more TB transmission in a two-step RA procedure). Absence of msg3-transfromPrecoding may indicate that it is disabled. numberOfRA-PreamblesGroupA may indicate a number of contention based (CB) preambles per SSB in group A. This may determine implicitly the number of CB preambles per SSB available in group B. The setting may be consistent with the setting of ssb-perRACH-OccasionAndCB-PreamblesPerSSB. prach-RootSequenceIndex may indicate PRACH root sequence index. There may be a layer 1 parameter (e.g., ‘PRACHRootSequenceIndex’) corresponding to ssb-perRACH-OccasionAndCB-PreamblePerSSB. The value range may depend on a size of preamble, e.g., whether a preamble length (L) is L=839 or L=139. ra-ContentionResolutionTimer may indicate an initial value for the contention resolution timer. For example, a value ms8 in RACH-ConfigCommon may indicate 8 ms, value ms16 may indicate 16 ms, and so on. ra-Msg3SizeGroupA may indicate a transport blocks size threshold in bit. For example, a wireless device may employ a contention based RA preamble of group A, for example, when the transport block size is below ra-Msg3SizeGroupA. rach-ConfigGeneric may indicate one or more generic RACH parameters in RACH-ConfigGeneric. restrictedSetConfig may indicate a configuration of an unrestricted set or one of two types of restricted sets. rsrp-ThresholdSSB may indicate a threshold for SS block selection. For example, a wireless device may select the SS block and corresponding PRACH resource for path-loss estimation and (re)transmission based on SS blocks that satisfy the threshold. rsrp-ThresholdSSB-SUL may indicate a threshold for uplink carrier selection. For example, a wireless device may select an SUL carrier to perform random access based on this threshold. ssb-perRACH-OccasionAndCB-PreamblesPerSSB may indicate a number of SSBs per RACH occasion and a number of contention based preambles per SSB. There may be layer 1 one or more parameters (e.g., ‘SSB-per-rach-occasion’ and/or ‘CB-preambles-per-SSB’) corresponding to ssb-perRACH-OccasionAndCB-PreamblesPerSSB. For example, a total number of CB preambles in a RACH occasion may be given by CB-preambles-per-SSB*max(1,SSB-per-rach-occasion). totalNumberOfRA-Preambles may indicate a total number of preambles employed for contention based and contention free random access. For example, totalNumberOfRA-Preambles may not comprise one or more preambles employed for other purposes (e.g. for SI request). A wireless device may use one or more of 64 preambles for RA, for example, if the field is absent.

An example random access common configuration of RACH-ConfigGeneric may be below:

RACH-ConfigGeneric ::= SEQUENCE {  prach-ConfigurationIndex INTEGER (0..255),  msg1-FDM ENUMERATED {one, two, four, eight},  msg1-FrequencyStart INTEGER (0..maxNrofPhysicalResourceBlocks-1),  zeroCorrelationZoneConfig INTEGER(0..15),  preambleReceivedTargetPower INTEGER (−202..−60),  preambleTransMax ENUMERATED {n3, n4, n5, n6, n7,n8, n10, n20, n50, n100, n200),  powerRampingStep ENUMERATED {dB0, dB2, dB4, dB6},  ra-ResponseWindow ENUMERATED {sl1, sl2, sl4, sl8, sl10, sl20, sl40, sl80},  ... }

For example, msg1-FDM may indicate a number of PRACH transmission occasions FDMed in one time instance. There may be a layer 1 parameter (e.g., ‘prach-FDM’) corresponding to msg1-FDM. msg1-FrequencyStart may indicate an offset of PRACH transmission occasion (e.g., lowest PRACH transmission occasion) in frequency domain with respective to a particular PRB (e.g., PRB 0). A base station may configure a value of msg1-FrequencyStart such that the corresponding RACH resource is within the bandwidth of the UL BWP. There may be a layer 1 parameter (e.g., ‘prach-frequency-start’) corresponding to msg1-FreqencyStart. powerRampingStep may indicate power ramping steps for PRACH. prach-ConfigurationIndex may indicate a PRACH configuration index. For example, a radio access technology (e.g., LTE, and/or NR) may predefine one or more PRACH configurations, and prach-ConfigurationIndex may indicate one of the one or more PRACH configurations. There may be a layer 1 parameter (e.g., ‘PRACHConfigurationIndex’) corresponding to prach-ConfigurationIndex. preambleReceivedTargetPower may indicate a target power level at the network receiver side. For example, multiples of a particular value (e.g., in dBm) may be chosen. RACH-ConfigGeneric above shows an example when multiples of 2 dBm are chosen (e.g. -202, -200, -198, . . . ). preambleTransMax may indicate a number of RA preamble transmissions performed before declaring a failure. For example, preambleTransMax may indicate a maximum number of RA preamble transmissions performed before declaring a failure. ra-ResponseWindow may indicate an RAR window length in number of slots (or subframes, mini-slots, and/or symbols). a base station may configure a value lower than or equal to a particular value (e.g., 10 ms). The value may be larger than a particular value (e.g., 10 ms). zeroCorrelationZoneConfig may indicate an index of preamble sequence generation configuration (e.g., N-CS configuration). A radio access technology (e.g., LTE and/or NR) may predefine one or more preamble sequence generation configurations, and zeroCorrelationZoneConfig may indicate one of the one or more preamble sequence generation configurations. For example, a wireless device may determine a cyclic shift of preamble sequence based on zeroCorrelationZoneConfig. zeroCorrelationZoneConfig may determine a property of random access preambles (e.g., a zero correlation zone)

An example random access dedicated configuration (e.g., RACH-ConfigDedicated) may be below:

RACH-ConfigDedicated ::= SEQUENCE {  cfra CFRA OPTIONAL, -- Need N  ra-Prioritization RA-Prioritization OPTIONAL, -- Need N  ... } CFRA ::= SEQUENCE {  occasions SEQUENCE {   rach-ConfigGeneric RACH-ConfigGeneric,   ssb-perRACH-Occasion ENUMERATED {oneEighth, oneFourth, oneHalf, one, two, four, eight, sixteen} OPTIONAL -- Cond SSB-CFRA  } OPTIONAL,-- Need S  resources CHOICE {   ssb SEQUENCE {    ssb-ResourceList SEQUENCE (SIZE(1..maxRA-SSB-Resources)) OF CFRA-SSB-Resource,    ra-ssb-OccasionMaskIndex INTEGER (0..15)   },   csirs SEQUENCE {    csirs-ResourceList SEQUENCE (SIZE(1..maxRA-CSIRS-Resources)) OF CFRA-CSIRS-Resource,    rsrp-ThresholdCSI-RS RSRP-Range   }  },  ... } CFRA-SSB-Resource ::= SEQUENCE {  ssb SSB-Index,  ra-PreambleIndex INTEGER (0..63),  ... } CFRA-CSIRS-Resource ::= SEQUENCE {  csi-RS CSI-RS-Index,  ra-OccasionList SEQUENCE (SIZE(1..maxRA-OccasionsPerCSIRS)) OF INTEGER (0..maxRA-Occasions-1),  ra-PreambleIndex INTEGER (0..63),  ... }

For example, csi-RS may indicate an identifier (e.g., ID) of a CSI-RS resource defined in the measurement object associated with this serving cell. ra-OccasionList may indicate one or more RA occasions. A wireless device may employ the one or more RA occasions, for example, when the wireless device performs a contention-free random access (CFRA) procedure upon selecting the candidate beam identified by this CSI-RS. ra-PreambleIndex may indicate an RA preamble index to use in the RA occasions associated with this CSI-RS. ra-ssb-OccasionMaskIndex may indicate a PRACH Mask Index for RA Resource selection. The mask may be valid for one or more SSB resources signaled in ssb-ResourceList. rach-ConfigGeneric may indicate a configuration of contention free random access occasions for the CFRA procedure. ssb-perRACH-Occasion may indicate a number of SSBs per RACH occasion. ra-PreambleIndex may indicate a preamble index that a wireless device may employ when performing CF-RA upon selecting the candidate beams identified by this SSB. ssb in RACH-ConfigDedicated may indicate an identifier (e.g., ID) of an SSB transmitted by this serving cell. cfra in RACH-ConfigDedicated may indicate one or more parameters for contention free random access to a given target cell. A wireless device may perform contention based random access, for example, if the field (e.g., cfra) is absent. ra-prioritization may indicate one or more parameters which apply for prioritized random access procedure to a given target cell. A field, SSB-CFRA, in RACH-ConfigDedicated may be present, for example, if the field resources in CFRA is set to ssb; otherwise it may be not present.

In an example, a base station may transmit one or more RRC message to configure a wireless device at least one of following parameters for a random access procedure:

-   -   prach-ConfigIndex: the available set of PRACH occasions for the         transmission of the Random Access Preamble     -   preambleReceivedTargetPower: initial Random Access Preamble         power;     -   rsrp-ThresholdSSB: an RSRP threshold for the selection of the         SSB and corresponding Random Access Preamble and/or PRACH         occasion. If the Random Access procedure is initiated for beam         failure recovery, rsrp-ThresholdSSB refers to rsrp-ThresholdSSB         in BeamFailureRecoveryConfig IE;     -   rsrp-ThresholdCSl-RS: an RSRP threshold for the selection of         CSI-RS and corresponding Random Access Preamble and/or PRACH         occasion. If the Random Access procedure is initiated for beam         failure recovery, rsrp-ThresholdCSl-RS shall be set to a value         calculated by multiplying rsrp-ThresholdSSB in         BeamFailureRecoveryConfig IE by powerControlOffset;         rsrp-ThresholdSSB-SUL: an RSRP threshold for the selection         between the NUL carrier and the SUL carrier;     -   powerControlOffset: a power offset between rsrp-ThresholdSSB and         rsrp-ThresholdCSl-RS to be employed when the Random Access         procedure is initiated for beam failure recovery;     -   powerRampingStep: the power-ramping factor;     -   powerRampingStepHighPriority: the power-ramping factor in case         of differentiated Random Access procedure     -   ra-PreambleIndex: an index of Random Access Preamble;     -   ra-ssb-OccasionMaskIndex: defines PRACH occasion(s) associated         with an SSB in which the MAC entity may transmit a Random Access         Preamble (FIG. 18 shows an example of ra-ssb-OccasionMaskIndex         values);     -   ra-OccasionList: defines PRACH occasion(s) associated with a         CSI-RS in which the MAC entity may transmit a Random Access         Preamble;     -   preambleTransMax: the maximum number of Random Access Preamble         transmission ssb-perRACH-OccasionAndCB-PreamblesPerSSB: defines         the number of SSBs mapped to each PRACH occasion and the number         of Random Access Preambles mapped to each SSB;     -   the set of Random Access Preambles and/or PRACH occasions for SI         request, if any;     -   the set of Random Access Preambles and/or PRACH occasions for         beam failure recovery request, if any;     -   ra-ResponseWindow: the time window to monitor RA response(s);         and/or     -   ra-ContentionResolutionTimer: the Contention Resolution Timer.

In an example, a random access procedure may be initiated for beam failure detection and recovery. For example, a wireless device may be configured by RRC with a beam failure recovery procedure which may be employed for indicating to the serving base station of a SSB or CSI-RS when beam failure is detected on the serving SSB(s)/CSI-RS(s). Beam failure may be detected by counting one or more beam failure instance indication from the lower layers to the MAC entity. For example, a base station may configure, via RRC, the following parameters in the BeamFailureRecoveryConfig for the Beam Failure Detection and Recovery procedure:

-   -   beamFailureInstanceMaxCount for the beam failure detection;     -   beamFailureDetectionTimer for the beam failure detection;     -   beamFailureRecoveryTimer for the beam failure recovery         procedure;     -   rsrp-ThresholdSSB: an RSRP threshold for the beam failure         recovery;     -   powerRampingStep: powerRampingStep for the beam failure         recovery;     -   preambleReceivedTargetPower: preambleReceivedTargetPower for the         beam failure recovery;     -   preambleTransMax: preambleTransMax for the beam failure         recovery;     -   ra-ResponseWindow: the time window to monitor response(s) for         the beam failure recovery using contention-free Random Access         Preamble;     -   prach-ConfigIndex: prach-ConfigIndex for the beam failure         recovery;     -   ra-ssb-OccasionMaskIndex: ra-ssb-OccasionMaskIndex for the beam         failure recovery; and/or     -   ra-OccasionList: ra-OccasionList for the beam failure recovery.

In an example, a wireless device may employ one or more parameters for a random access procedure. For example, a wireless device may employ at least one of PREAMBLE_INDEX; PREAMBLE_TRANSMISSIONP_COUNTER; PREAMBLE_POWER_RAMPING_COUNTER; PREAMBLE_POWER_RAMPING_STEP; PREAMBLE_RECEIVED_TARGET_POWER; PREAMBLE-BACKOFF; PCMAX; SCALING_FACTOR_BI; and TEMPORARY_C-RNTI.

In an example, a wireless device may perform random access resource selection for selecting one or more preambles and one or more PRACH occasion (or resources comprising time, frequency, and/or code). For example, there may be one or more cases that a random access procedure may be initiated for beam failure recovery; and/or the beamFailureRecoveryTimer is either running or not configured; and/or the contention-free Random Access Resources for beam failure recovery request associated with any of the SSBs and/or CSI-RS s have been explicitly provided by RRC; and/or at least one of the SSBs with SS-RSRP above rsrp-ThresholdSSB amongst the SSBs in candidateBeamRSList or the CSI-RSs with CSI-RSRP above rsrp-ThresholdCSl-RS amongst the CSI-RSs in candidateBeamRSList is available. In this case, a wireless device may select an SSB with SS-RSRP above rsrp-ThresholdSSB amongst the SSBs in candidateBeamRSList or a CSI-RS with CSI-RSRP above rsrp-ThresholdCSl-RS amongst the CSI-RSs in candidateBeamRSList. For example, if CSI-RS is selected, and there is no ra-PreambleIndex associated with the selected CSI-RS, a wireless device may set the PREAMBLE_INDEX to a ra-PreambleIndex corresponding to the SSB in candidateBeamRSList which is quasi-collocated with the selected CSI-RS, otherwise the wireless device may set the PREAMBLE_INDEX to a ra-PreambleIndex corresponding to the selected SSB or CSI-RS from the set of Random Access Preambles for beam failure recovery request.

For example, there may be one or more cases that a random access procedure may be initiated and/or a ra-PreambleIndex has been explicitly provided by either PDCCH or RRC; and/or the ra-PreambleIndex is not a first preamble index (that may be predefined or configured e.g., 0b000000); and/or contention-free Random Access Resource associated with SSBs or CSI-RSs have not been explicitly provided by RRC. In this case, a wireless device may set the PREAMBLE_INDEX to the signaled ra-PreambleIndex.

For example, there may be one or more cases that a random access procedure may be initiated and/or the contention-free Random Access Resources associated with SSBs have been explicitly provided by RRC and at least one SSB with SS-RSRP above rsrp-ThresholdSSB amongst the associated SSBs is available. In this case, a wireless device may select an SSB with SS-RSRP above rsrp-ThresholdSSB amongst the associated SSBs. For example, the wireless device may set the PREAMBLE_INDEX to a ra-PreambleIndex corresponding to the selected SSB.

For example, there may be one or more cases that a random access procedure may be initiated and the contention-free random access resources associated with CSI-RSs have been explicitly provided by RRC and at least one CSI-RS with CSI-RSRP above rsrp-ThresholdCSl-RS amongst the associated CSI-RSs is available. In this case, a wireless device may select a CSI-RS with CSI-RSRP above rsrp-ThresholdCSl-RS amongst the associated CSI-RSs. for example, the wireless device may set the PREAMBLE_INDEX to a ra-PreambleIndex corresponding to the selected CSI-RS.

For example, there may be one or more cases that a random access procedure may be initiated and at least one of the SSBs with SS-RSRP above rsrp-ThresholdSSB is available. In this case, for example, a wireless device may select an SSB with SS-RSRP above rsrp-ThresholdSSB, otherwise may select any SSB. For example, a random access resource selection is performed when Msg 3 1240, two-step Msg 1 1620, and/or one or more TBs 1640 is being retransmitted, a wireless device may select the same group of Random Access Preambles as was employed for the Random Access Preamble transmission attempt corresponding to the first transmission of Msg 3, two-step Msg 1 1620, and/or one or more TBs 1640. For example, if the association between random access preambles and SSBs is configured, a wireless device may select a ra-PreambleIndex randomly with equal probability from the Random Access Preambles associated with the selected SSB and the selected Random Access Preambles group. For example, if the association between random access preambles and SSBs is not configured, a wireless device may select a ra-PreambleIndex randomly with equal probability from the Random Access Preambles within the selected Random Access Preambles group. For example, a wireless device may set the PREAMBLE_INDEX to the selected ra-PreambleIndex.

In an example, if an SSB is selected above and an association between PRACH occasions and SSBs is configured, a wireless device may determine the next available PRACH occasion from the PRACH occasions corresponding to the selected SSB permitted by the restrictions given by the ra-ssb-OccasionMaskIndex if configured (the MAC entity of the wireless device may select a PRACH occasion randomly with equal probability amongst the PRACH occasions occurring simultaneously but on different subcarriers, corresponding to the selected SSB; the MAC entity may take into account the possible occurrence of measurement gaps when determining the next available PRACH occasion corresponding to the selected SSB).

In an example, if a CSI-RS is selected above and an association between PRACH occasions and CSI-RSs is configured. a wireless device may determine the next available PRACH occasion from the PRACH occasions in ra-OccasionList corresponding to the selected CSI-RS (the MAC entity shall select a PRACH occasion randomly with equal probability amongst the PRACH occasions occurring simultaneously but on different subcarriers, corresponding to the selected CSI-RS; the MAC entity may take into account the possible occurrence of measurement gaps when determining the next available PRACH occasion corresponding to the selected CSI-RS).

In an example, if a CSI-RS is selected above and there is no contention-free Random Access Resource associated with the selected CSI-RS, a wireless device may determine the next available PRACH occasion from the PRACH occasions, permitted by the restrictions given by the ra-ssb-OccasionMaskIndex if configured, corresponding to the SSB in candidateBeamRSList which is quasi-collocated with the selected CSI-RS (the MAC entity may take into account the possible occurrence of measurement gaps when determining the next available PRACH occasion corresponding to the SSB which is quasi-collocated with the selected CSI-RS).

For example, a wireless device may determine the next available PRACH occasion (the MAC entity shall select a PRACH occasion randomly with equal probability amongst the PRACH occasions occurring simultaneously but on different subcarriers; the MAC entity may take into account the possible occurrence of measurement gaps when determining the next available PRACH occasion).

For example, based on a selected PREABLE INDEX and PRACH occasion, a wireless device may perform the random access preamble transmission. For example, if the notification of suspending power ramping counter has not been received from lower layers; and/or if SSB selected is not changed (i.e. same as the previous Random Access Preamble transmission), a wireless device may increment PREAMBLE_POWER_RAMPING_COUNTER by 1. the wireless device may select a value of DELTA_PREAMBLE that may be predefined and/or semi-statically configured by a base station and set PREAMBLE_RECEIVED_TARGET_POWER to preambleReceivedTargetPower+DELTA_PREAMBLE+(PREAMBLE_POWER_RAMPING_COUNTER−1)×PREAMBLE_POWER_RAMPING_STEP.

The wireless device may instruct the physical layer to transmit the Random Access Preamble using the selected PRACH, corresponding RA-RNTI (if available), PREAMBLE_INDEX and PREAMBLE_RECEIVED_TARGET_POWER. For example, the wireless device may compute an RA-RNTI associated with the PRACH occasion in which the Random Access Preamble is transmitted, e.g., In an example, the RA-RNTI associated with the PRACH in which the Random Access Preamble is transmitted, may be computed in terms of index of the first OFDM symbol of the specified PRACH, an index of the first slot of the specified PRACH in a system frame, an index of the specified PRACH in the frequency domain, and/or uplink carrier indicator. For example, an example the RA-RNTI is:

RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id

where s_id is the index of the first OFDM symbol of the specified PRACH (0≤s_id<14), t_id is the index of the first slot of the specified PRACH in a system frame (0≤t_id<80), f_id is the index of the specified PRACH in the frequency domain (0≤f_id<8), and ul_carrier_id is the UL carrier used for Msg 1 1220 transmission or two-step Msg 1 1620 (0 for NUL carrier, and 1 for SUL carrier).

The amount of data traffic carried over cellular networks is expected to increase for many years to come. The number of users/devices is increasing and each user/device accesses an increasing number and variety of services, e.g. video delivery, large files, images. This requires not only high capacity in the network, but also provisioning very high data rates to meet customers' expectations on interactivity and responsiveness. More spectrum is therefore needed for cellular operators to meet the increasing demand. Considering user expectations of high data rates along with seamless mobility, it is beneficial that more spectrum be made available for deploying macro cells as well as small cells for cellular systems.

Striving to meet the market demands, there has been increasing interest from operators in deploying some complementary access utilizing unlicensed spectrum to meet the traffic growth. This is exemplified by the large number of operator-deployed Wi-Fi networks and the 3GPP standardization of interworking solutions with Wi-Fi, e.g., LTE/WLAN interworking. This interest indicates that unlicensed spectrum, when present, can be an effective complement to licensed spectrum for cellular operators to help addressing the traffic explosion in some scenarios, such as hotspot areas. For example, in a legacy system (e.g., LTE), licensed assisted access (LAA) and/or new radio on unlicensed band(s) (NR-U) may offer an alternative for operators to make use of unlicensed spectrum while managing one radio network, thus offering new possibilities for optimizing the network's efficiency.

In an example embodiment, Listen-before-talk (LBT) may be implemented for transmission in a cell configured in unlicensed band (referred to as a LAA cell and/or a NR-U cell for the sake of convenience, for example, an LAA cell and NR-U cell may be interchangeable and may refer any cell operating in unlicensed band. The cell may be operated as non-standalone with an anchor cell in licensed band or standalone without an anchor cell in licensed band). The LBT may comprise a clear channel assessment. For example, in an LBT procedure, equipment may apply a clear channel assessment (CCA) check before using the channel. For example, the CCA utilizes at least energy detection to determine the presence or absence of other signals on a channel in order to determine if a channel is occupied or clear, respectively. A regulation of a country may impact on the LBT procedure. For example, European and Japanese regulations mandate the usage of LBT in the unlicensed bands, for example in 5GHz unlicensed band. Apart from regulatory requirements, carrier sensing via LBT may be one way for fair sharing of the unlicensed spectrum.

In an example embodiment, discontinuous transmission on an unlicensed carrier with limited maximum transmission duration may be enabled. Some of these functions may be supported by one or more signals to be transmitted from the beginning of a discontinuous downlink transmission in the unlicensed band. Channel reservation may be enabled by the transmission of signals, by an NR-U node, after gaining channel access via a successful LBT operation, so that other nodes that receive the transmitted signal with energy above a certain threshold sense the channel to be occupied. Functions that may need to be supported by one or more signals for operation in unlicensed band with discontinuous downlink transmission may include one or more of the following: detection of the downlink transmission in unlicensed band (including cell identification) by wireless devices; time and frequency synchronization of a wireless devices.

In an example embodiment, DL transmission and frame structure design for an operation in unlicensed band may employ subframe or slot boundary alignment according to carrier aggregation timing relationships across serving cells aggregated by CA. This may not imply that the base station transmissions start at the subframe or slot boundary. LAA and/or NR-U cell may transmitting data via PDSCH when not all OFDM symbols are available for transmission in a subframe or a slot. Delivery of necessary control information for the PDSCH may be supported.

An LBT procedure may be employed for fair and friendly coexistence of wireless system (e.g., LTE and/or NR) with other operators and technologies operating in unlicensed spectrum. LBT procedures on a node attempting to transmit on a carrier (or a channel) in unlicensed spectrum require the node to perform a clear channel assessment to determine if the channel is free for use. An LBT procedure may involve at least wireless signal energy detection to determine if the channel is being used. For example, regulatory requirements in some regions, e.g., in Europe, specify an energy detection threshold such that if a measured energy on a carrier (or a channel) is greater than this threshold, the node assumes that the channel is not free (used by other node(s)). A node may optionally employ a lower threshold for energy detection than that specified by regulatory requirements. In an example, NR-U may employ a mechanism to adaptively change the energy detection threshold, e.g., NR-U may employ a mechanism to adaptively lower the energy detection threshold from an upper bound. Adaptation mechanism may not preclude static or semi-static setting of the threshold. In an example Category 4 LBT mechanism or other type of LBT mechanisms may be implemented.

Various example LBT mechanisms may be implemented. In an example, for some signals, in some implementation scenarios, in some situations, and/or in some frequencies no LBT procedure may performed by the transmitting entity. In an example, Category 1 (CAT1, e.g., no LBT) may be implemented in one or more cases. For example, a channel in unlicensed band is hold by a base station for DL transmission, and a wireless device takes over it for UL transmission, the wireless device may perform the UL transmission with no LBT. In an example, Category 2 (CAT2, e.g. LBT without random back-off) may be implemented. The duration of time that the channel is sensed to be idle before the transmitting entity transmits may be deterministic. In an example, Category 3 (CAT3, e.g. LBT with random back-off with a contention window of fixed size) may be implemented. The LBT procedure may have the following procedure as one of its components. The transmitting entity may draw a random number N within a contention window. The size of the contention window may be specified by the minimum and maximum value of N. The size of the contention window may be fixed. The random number N may be employed in the LBT procedure to determine the duration of time that the channel is sensed to be idle before the transmitting entity transmits on the channel. In an example, Category 4 (CAT4, e.g. LBT with random back-off with a contention window of variable size) may be implemented. The transmitting entity may draw a random number N within a contention window. The size of contention window may be specified by the minimum and maximum value of N. The transmitting entity may vary the size of the contention window when drawing the random number N. The random number N is used in the LBT procedure to determine the duration of time that the channel is sensed to be idle before the transmitting entity transmits on the channel.

In an example, a wireless device may employ an uplink LBT for uplink transmissions on an unlicensed band. The UL LBT may be different from the DL LBT (e.g. by using different LBT mechanisms and/or parameters). For example, the UL LBT may be based on scheduled access that may affect a wireless device's channel contention opportunities. Other considerations motivating a different UL LBT include, but are not limited to, multiplexing of multiple wireless devices in a subframe (slot, and/or mini-slot).

In an example, a DL transmission burst may be a continuous transmission from a DL transmitting node with no transmission immediately before or after from the same node on the same carrier component (CC). An UL transmission burst from a wireless device perspective may be a continuous transmission from a wireless device with no transmission immediately before or after from the same wireless device on the same CC. In an example, UL transmission burst is defined from a wireless device perspective. In an example, an UL transmission burst may be defined from a base station perspective. In an example, in case of a base station operating DL and UL transmissions over the same unlicensed carrier, DL transmission burst(s) and UL transmission burst(s) may be scheduled in a TDM manner over the same unlicensed carrier. For example, an instant in time may be part of a DL transmission burst and/or an UL transmission burst.

Channel observation time (COT) sharing may be employed in an operation in an unlicensed band. COT sharing is a mechanism (e.g., enabled by ETSI-BRAN) wherein one device acquires a COT using CAT4 LBT and another device shares it using a 25 us LBT with a gap provided the amount of transmission does not exceed a limit of COT (e.g., maximum COT (MCOT)) for the given priority class. COT sharing may allow a concession for UL in unlicensed band in which a base station transmit a UL grant to a wireless device before it can transmit on the UL and the delay between the UL grant and the corresponding UL transmission is a certain period of time, e.g., at least 4ms. This pause (e.g., 4 ms) may not be accounted in the COT duration. For example, if a base station acquired a COT and transmitted on the DL without exhausting the full COT, it may indicate to one or more wireless devices via PDCCH. The wireless device may perform UL transmissions with dynamic grant and/or configured grant (e.g., Type 1, Type2, autonomous UL) with a short (e.g., 25 us) LBT in the configured period

In an example, one or more DL to UL and UL to DL switching within a shared COT may be supported. Example LBT requirements to support one or more switching points, may comprise: for gap of less than a first threshold (e.g., 16 us): no-LBT may be used; for gap of above the first threshold (e.g., 16 us) but does not exceed a second threshold (e.g., 25 us): one-shot LBT may be employed; for single switching point, for the gap from DL transmission to UL transmission exceeds the second threshold (e.g., 25us): one-shot LBT may be employed ; for multiple switching points, for the gap from DL transmission to UL transmission exceeds the second threshold (e.g., 25 us), one-shot LBT may be employed.

In an example, a signal that facilitates its detection with low complexity may be useful for wireless device power saving; Improved coexistence; Spatial reuse at least within the same operator network, Serving cell transmission burst acquisition, etc. In an example, operation of NR-U may employ a signal comprising at least SS/PBCH block burst set transmission. In an example, other channels and signals may be transmitted together as part of the signal. The design of this signal may consider there are no gaps within the time span the signal is transmitted at least within a beam. In an example, gaps may be needed for beam switching. In an example, the occupied channel bandwidth may be satisfied. In an example, a block-interlaced based PUSCH may be employed. In an example, the same interlace structure for PUCCH and PUSCH may be used. In an example, interlaced based PRACH may be used.

In an example, initial active DL/UL BWP may be approximately 20 MHz for a first unlicensed band, e.g., 5GHz band. In an example, initial active DL/UL BWP may be approximately 20 MHz for a second unlicensed band, e.g., 6 GHz band, if similar channelization as the first unlicensed band, e.g., 5 GHz band is used for the second unlicensed band, e.g., 6 GHz band. For a wideband case, a base station may configure the wideband with one or more BWP. For example, for 80 MHz case, a base station may configure four BWPs; each BWP may be configured with about 20 MHz. An active BWP (DL and/or UL) may be switched one to another at least based on BWP switching mechanism. For example, a base station may configure the wideband with one or more subbands. For example, for 80 MHz case, a base station may configure four subbands; each subband may be configured with about 20 MHz. For example, a wireless device may perform an LBT subband by subband, and may transmit data via scheduled resources on one or more subbands where the LBT indicates idle.

In an example, a HARQ feedback, e.g., positive acknowledge and negative acknowledge (A/N), for the corresponding data may be transmitted in the same shared COT. In some examples, the HARQ A/N may be transmitted in a separate COT from the one the corresponding data was transmitted. In an example, when UL HARQ feedback is transmitted on unlicensed band, NR-U may consider mechanisms to support flexible triggering and multiplexing of HARQ feedback for one or more DL HARQ processes. In an example, the dependencies of HARQ process information to the timing may be removed. In an example, UCI on PUSCH may carry HARQ process ID, NDI, RVID. In an example, Downlink Feedback Information (DFI) may be used for transmission of HARQ feedback for configured grant.

In an example, contention-based random access (CBRA) and/or contention-free random access (CFRA) may be supported on SpCell. CFRA may be supported on SCells. In an example, an RAR may be transmitted via SpCell, e.g., non-standalone scenario. In an example, an RAR may be transmitted via SpCell and/or SCell, e.g., standalone scenario. In an example, a predefined HARQ process ID for an RAR.

In an example, carrier aggregation between PCell configured on licensed band and SCell configured on unlicensed band may be supported. In an example, SCell may have both DL and UL, or DL-only. In an example, dual connectivity between PCell (e.g., LTE cell) configured on licensed band and PSCell (e.g., NR-U cell) configured on unlicensed band may be supported. In an example, Stand-alone operation on an unlicensed band, where all carriers are in one or more unlicensed bands, may be supported. In an example, a cell with DL in unlicensed band and UL in licensed band or vice versa may be supported. In an example, dual connectivity between PCell (e.g., NR cell) on licensed band and PSCell (e.g., NR-U cell) on unlicensed band may be supported.

In an example, if absence of Wi-Fi cannot be guaranteed (e.g. by regulation) in a band (e.g., sub-7 GHz) where NR-U is operating, the NR-U operating bandwidth may be an integer multiple of 20 MHz. In an example, at least for band where absence of Wi-Fi cannot be guaranteed (e.g. by regulation), LBT may be performed in units of 20 MHz. In an example, receiver assisted LBT (e.g., RTS/CTS type mechanism) and/or on-demand receiver assisted LBT (e.g., for example receiver assisted LBT enabled only when needed) may be employed. In an example, techniques to enhance spatial reuse may be used. In an example, preamble detection may be used.

In an example, with scheduled PUSCH transmissions on an unlicensed carrier, the network may need to gain access to the channel to transmit PDCCH and then a wireless device may perform LBT again prior to transmitting on the resource. Such procedure tends to increase latency especially when the channel is loaded. In an example, a mechanism of autonomous uplink transmission may be used. In an example, a wireless device may be configured (by a base station) with one or more resources (maybe periodic resources) for transmission similar to UL configured grant (Type 1 and/or Type 2 and/or LTE UL SPS) and perform LBT prior to using the resource. In an example, autonomous uplink may be based on the Configured Grant functionality (e.g., Type 1 and/or Type 2).

In an example, the HARQ process identity may be transmitted by the wireless device (e.g., as UCI). This may enable a wireless device to use the first available transmission opportunity irrespective of the HARQ process. In an example, UCI on PUSCH may be used to carry HARQ process ID, NDI and RV ID.

For unlicensed band, UL dynamic grant scheduled UL transmission may increase the delay and transmission failure possibility due to at least two LBTs of wireless device and gNB perform. Pre-configured grant such as configured grant in NR may be used for NR-U. The pre-configured grant may decrease the number of LBTs performed and control signaling overhead. In an example, in a Type 1 configured grant, an uplink grant is provided by an RRC, and stored as configured uplink grant. The Type 1 configured grant may be initiated in response to receiving the RRC. In an example, in a Type 2 configured grant, an uplink grant may be provided by PDCCH, and stored or cleared as configured uplink grant based on L1 signaling indicating configured grant activation or deactivation.

In an example, there may not be a dependency between HARQ process information to the timing. In an example, UCI on PUSCH may carry HARQ process ID, NDI, RVID, etc. In an example, wireless device may autonomously select one HARQ process ID which is informed to a base station by UCI. In an example, a wireless device may perform non-adaptive retransmission with the configured uplink grant. When dynamic grant for configured grant retransmission is blocked due to LBT, wireless device may try to transmit in the next available resource with configured grant.

In an example, Downlink Feedback Information (DFI) may be transmitted (e.g., using DCI) may include HARQ feedback for configured grant transmission. The wireless device may perform transmission/retransmission using configured grant based on DFI comprising one or more HARQ feedbacks.

In an example, wideband carrier with more than one channels (e.g., subbands) is supported on NR-based unlicensed cell. In an example, there may be one active BWP in a carrier. In an example, a BWP with one or more channels may be activated. In an example, when absence of Wi-Fi cannot be guaranteed (e.g. by regulation), LBT may be performed in units of 20 MHz. In this case, there may be multiple parallel LBT procedures for this BWP. The actual transmission bandwidth may be subject to subband with LBT success, which may result in dynamic bandwidth transmission within this active wideband BWP.

In an example, one or more active BWPs may be supported. To improve the BWP utilization efficiency, the BWP bandwidth may be the same as the bandwidth of subband for LBT, e.g., LBT may be carried out on each BWP. The network may activate/deactivate the BWPs based on data volume to be transmitted.

In an example, one or more non-overlapped BWPs may be activated for a wireless device within a wide component carrier, which may be similar as carrier aggregation. To improve the BWP utilization efficiency, the BWP bandwidth may be the same as the bandwidth of subband for LBT, i.e. LBT may be carried out on each BWP. When more than one subband LBT success, it requires a wireless device to have the capability to support one or more narrow RF or a wide RF which may comprise the one or more activated BWPs.

In an example, a single wideband BWP may be activated for a wireless device within a component carrier. The bandwidth of wideband BWP may be in the unit of subband for LBT. For example, if the subband for LBT is 20 MHz in 5 GHz band, the wideband BWP bandwidth may comprise multiple 20 MHz.The actual transmission bandwidth may be subject to subband with LBT success, which may result in dynamic bandwidth transmission within this active wideband BWP.

In an example, active BWP switching may be achieved by use of scheduling DCI. In an example, the network may indicate to a wireless device a new active BWP to use for an upcoming, and any subsequent, data transmission/reception. In an example, a wireless device may monitor multiple, configured BWPs to determine which has been acquired for DL transmissions by the base station. For example, a wireless device may be configured with monitoring occasion periodicity and offset for each configured BWP. The wireless device may attempt to determine if a BWP has been acquired by the base station during those monitoring occasions. In an example, upon determining that the channel is acquired, the wireless device may continue with that BWP as its active BWP, at least until indicated otherwise or Maximum Channel Occupancy Time (MCOT) has been reached. In an example, when a wireless device has determined that a BWP is active, it may attempt blind detection of PDCCH in configured CORESETs and it might also perform measurements on aperiodic or periodic resources (e.g., Type 1 or Type 2 configured grant).

In an example, for UL transmissions, a wireless device may be configured with multiple UL resources, possibly in one or more BWPs. The wireless device may have multiple LBT configurations, each tied to a BWP and possibly a beam pair link. The wireless device may be granted UL resources tied to one or more LBT configurations. Similarly, the wireless device may be provided with multiple resources for autonomous uplink (AUL), configured grant Type 1, and/or configured grant Type 2; each requiring the use of different LBT configurations. Providing a wireless device with multiple AUL resources over multiple BWPs may ensure that if LBT fails using a first LBT configuration for one AUL resource in one BWP, a wireless device can attempt transmission in another AUL resource in another BWP. This may reduce the channel access latency and make better use of the over-all unlicensed carrier.

The carrier aggregation with at least one SCell operating in the unlicensed spectrum may be referred to as Licensed-Assisted Access (LAA). In LAA, the configured set of serving cells for a wireless device may include at least one SCell operating in the unlicensed spectrum according to a first frame structure (e.g., frame structure Type 3 in LTE). The SCell may be called LAA SCell.

In an example, which LBT type (e.g., type 1 or type 2 uplink channel access) the wireless device applies may be signaled via uplink grant for uplink PUSCH transmission on LAA SCells. In an example, for preconfigured grant (e.g., AUL, configured grant type 1, and/or configured grant type 2) transmissions, the LBT may not be signaled in the uplink grant.

In an example, for type 1 uplink channel access, base station may signal the Channel Access Priority Class for a logical channel and a wireless device may select the highest Channel Access Priority Class (e.g., with a lower number in FIG. 19) of the logical channel(s) with MAC SDU multiplexed into the MAC PDU. In an example, the MAC CEs except padding BSR may use the lowest Channel Access Priority Class.

In an example, for type 2 uplink channel access on AUL, the wireless device may select logical channels corresponding to any Channel Access Priority Class for UL transmission in the subframes signaled by base station in common downlink control signaling.

In an example, for uplink LAA operation, the base station may not schedule the wireless device one or more subframes or slots than the minimum necessary to transmit the data corresponding to the selected Channel Access Priority Class or lower (e.g., with a lower number in FIG. 19), than the channel Access Priority Class signaled in UL grant based on the latest BSR and received uplink traffic from the wireless device if type 1 uplink channel access procedure is signaled to the wireless device; and/or Channel Access Priority Class used by the base station based on the downlink traffic, the latest BSR and received UL traffic from the wireless device if type 2 uplink channel access procedure is signaled to the wireless device.

In an example, a first number (e.g., four) Channel Access Priority Classes may be used when performing uplink and downlink transmissions in LAA carriers. In an example in FIG. 19 shows which Channel Access Priority Class may be used by traffic belonging to the different standardized QCIs. A non-standardized QCI (e.g., Operator specific QCI) may use suitable Channel Access Priority Class based on the FIG. 19 for example, e.g., the Channel Access Priority Class used for a non-standardized QCI should be the Channel Access Priority Class of the standardized QCIs which best matches the traffic class of the non-standardized QCI. In an example, for uplink, the base station may select the Channel Access Priority Class by taking into account the lowest priority QCI in a Logical Channel Group.

In an example, four Channel Access Priority Classes may be used. If a DL transmission burst with PDSCH is transmitted, for which channel access has been obtained using Channel Access Priority Class P (1 . . . 4), the base station may ensure the following where a DL transmission burst refers to the continuous transmission by base station after a successful LBT: the transmission duration of the DL transmission burst may not exceed the minimum duration needed to transmit all available buffered traffic corresponding to Channel Access Priority Class(es)≤P; the transmission duration of the DL transmission burst may not exceed the Maximum Channel Occupancy Time for Channel Access Priority Class P; and additional traffic corresponding to Channel Access Priority Class(s)>P may be included in the DL transmission burst once no more data corresponding to Channel Access Priority Class≤P is available for transmission. In such cases, base station may maximize occupancy of the remaining transmission resources in the DL transmission burst with this additional traffic.

In an example, when the PDCCH of an LAA SCell is configured, if cross-carrier scheduling applies to uplink transmission, it may be scheduled for downlink transmission via its PDCCH and for uplink transmission via the PDCCH of one other serving cell. In an example, when the PDCCH of an LAA SCell is configured, if self-scheduling applies to both uplink transmission and downlink transmission, it may be scheduled for uplink transmission and downlink transmission via its PDCCH.

In a RA procedure, a wireless device may receive from a base station at least one RAR as a response of Msg 1 1220 or two-step Msg 1 1620. An RAR may be in a form of MAC PDU comprising one or more MAC subPDUs and optionally padding. FIG. 20A is an example of an RAR. A MAC subheader may be octet aligned. Each MAC subPDU may comprise at least one of following: a MAC subheader with Backoff Indicator only; a MAC subheader with RAPID only (i.e. acknowledgment for SI request); a MAC subheader with RAPID and MAC RAR. FIG. 20B is an example of a MAC subheader with backoff indicator. For example, a MAC subheader with backoff indicator comprise one or more header fields, e.g., E/T/R/R/BI as described in FIG. 20B. A MAC subPDU with backoff indicator may be placed at the beginning of the MAC PDU, if included. MAC subPDU(s) with RAPID only and MAC subPDU(s) with RAPID and MAC RAR may be placed anywhere after MAC subPDU with Backoff Indicator and, if exist before padding as described in FIG. 20A. A MAC subheader with RAPID may comprise one or more header fields, e.g., E/T/RAPID as described in FIG. 20C. Padding may be placed at the end of the MAC PDU if present. Presence and length of padding may be implicit based on TB size, size of MAC subPDU(s).

In an example one or more header fields in a MAC subheader may indicate as follow: an E field may indicate an extension field that may be a flag indicating if the MAC subPDU including this MAC subheader is the last MAC subPDU or not in the MAC PDU. The E field may be set to “1” to indicate at least another MAC subPDU follows. The E field may be set to “0” to indicate that the MAC subPDU including this MAC subheader is the last MAC subPDU in the MAC PDU; a T filed may be a flag indicating whether the MAC subheader contains a Random Access Preamble ID or a Backoff Indicator (one or more backoff values may predefined and BI may indicate one of backoff value). The T field may be set to “0” to indicate the presence of a Backoff Indicator field in the subheader (BI). The T field may be set to “1” to indicate the presence of a Random Access Preamble ID field in the subheader (RAPID); an R filed may indicate a reserved bit that may be set to “0”; a BI field may be a backoff indicator field that identifies the overload condition in the cell. The size of the BI field may be 4 bits; an RAPID field may be a Random Access Preamble IDentifier field that may identify the transmitted Random Access Preamble. If the RAPID in the MAC subheader of a MAC subPDU corresponds to one of the Random Access Preambles configured for SI request, MAC RAR may not be included in the MAC subPDU.

There may be one or more MAC RAR format. At least one of following MAC RAR format may be employed in a four-step or a two-step RA procedure. For example, FIG. 21 is an example of one of MAC RAR formats. The MAC RAR may be fixed size as depicted in FIG. 21 and may comprise at least one of the following fields: an R field that may indicate a Reserved bit, set to “0”; a Timing Advance Command field that may indicate the index value TA employed to control the amount of timing adjustment; a UL Grantfield that indicate the resources to be employed on the uplink; and a RNTI field (e.g., Temporary C-RNTI and/or C-RNTI) that may indicate an identity that is employed during Random Access. For example, for a two-step RA procedure, an RAR may comprise at least one of following: a UE contention resolution identity, an RV ID for retransmission of one or more TB s, decoding success or failure indicator of one or more TB transmission, and one or more fields described in FIG. 21.

There may be a case that a base station may multiplex, in a MAC PDU, RARs for two-step and four-step RA procedures. If RARs for two-step and four-step RA procedure have the same size, a wireless device may not require an RAR length indicator field and/or the wireless device may determine the boundary of each RAR in the MAC PDU based on pre-determined RAR size information. For example, FIG. 22 is an example RAR format that may be employed in a MAC PDU multiplexing RARs for two-step and four-step RA procedures. The RAR shown in FIG. 22 may be a fixed size using the same format for two-step and four-step RA procedures.

In an example, an RAR for a two-step RA procedure may have a different format, size, and/or fields, from an RAR for a four-step RA procedure. For example, FIG. 23A, and FIG. 23B are example RAR formats that may be employed for a two-step RA procedure. If RARs for two-step and four-step RA procedures are multiplexed into a MAC PDU, and the RARs have different format between two-step and four-step RA procedure, an RAR may have a field to indicate a type of RAR (e.g., a reserved “R” field as shown in FIG. 21, FIG. 23A, and FIG. 23B may be employed to indicate a type of RAR). A field for indicating an RAR type may be in a subheader (such as a MAC subheader) or in an RAR. An RAR may comprise different types of fields that may correspond with an indicator in a subheader or in an RAR. A wireless device may determine the boundary of one or more RARs in a MAC PDU based on one or more indicators.

In an example, a Serving Cell may be configured with one or multiple BWPs. In an example, a maximum number of BWP per Serving Cell may be a first number.

In an example, the BWP switching for a Serving Cell may be used to activate an inactive BWP and deactivate an active BWP at a time. In an example, the BWP switching may be controlled by the PDCCH indicating a downlink assignment or an uplink grant, by the bwp-InactivityTimer, by RRC signaling, or by the MAC entity itself upon initiation of Random Access procedure. In an example, upon/in response to addition of SpCell or activation of an SCell, the DL BWP and UL BWP indicated by firstActiveDownlinkBWP-Id and firstActiveUplinkBWP-Id respectively may be active without receiving PDCCH indicating a downlink assignment or an uplink grant. The active BWP for a Serving Cell may be indicated by either RRC or PDCCH. For unpaired spectrum, a DL BWP may be paired with a UL BWP, and BWP switching may be common for both UL and DL.

In an example, for an activated Serving Cell configured with a BWP, if a BWP is activated, the MAC entity may transmit on UL-SCH on the BWP; may transmit on RACH on the BWP; may monitor the PDCCH on the BWP; may transmit PUCCH on the BWP; may transmit SRS on the BWP; may receive DL-SCH on the BWP; and may (re-)initialize any suspended configured uplink grants of configured grant Type 1 on the active BWP according to the stored configuration, if any, and to start in a symbol.

In an example, for an activated Serving Cell configured with a BWP, if a BWP is deactivated, the MAC entity may not transmit on UL-SCH on the BWP; may not transmit on RACH on the BWP; may not monitor the PDCCH on the BWP; may not transmit PUCCH on the BWP; may not report CSI for the BWP; may not transmit SRS on the BWP; may not receive DL-SCH on the BWP; may clear any configured downlink assignment and configured uplink grant of configured grant Type 2 on the BWP; and may suspend any configured uplink grant of configured grant Type 1 on the inactive BWP.

In an example, upon/in response to initiation of the Random Access procedure on a Serving Cell, if PRACH occasions are not configured for the active UL BWP, the MAC entity may switch the active UL BWP to BWP indicated by initialUplinkBWP and if the Serving Cell is a SpCell, the MAC entity may switch the active DL BWP to BWP indicated by initialDownlinkBWP. The MAC entity may perform the Random Access procedure on the active DL BWP of SpCell and active UL BWP of this Serving Cell.

In an example, upon/in response to initiation of the Random Access procedure on a Serving Cell, if PRACH occasions are configured for the active UL BWP, if the Serving Cell is a SpCell and if the active DL BWP does not have the same bwp-Id as the active UL BWP, the MAC entity may switch the active DL BWP to the DL BWP with the same bwp-Id as the active UL BWP. The MAC entity may perform the Random Access procedure on the active DL BWP of SpCell and active UL BWP of this Serving Cell.

In an example, if the MAC entity receives a PDCCH for BWP switching of a serving cell, if there is no ongoing Random Access procedure associated with this Serving Cell; or if the ongoing Random Access procedure associated with this Serving Cell is successfully completed upon reception of this PDCCH addressed to C-RNTI the MAC entity may perform BWP switching to a BWP indicated by the PDCCH.

In an example, if the MAC entity receives a PDCCH for BWP switching for a Serving Cell while a Random Access procedure associated with that Serving Cell is ongoing in the MAC entity, it may be up to a wireless device implementation whether to switch BWP or ignore the PDCCH for BWP switching, except for the PDCCH reception for BWP switching addressed to the C-RNTI for successful Random Access procedure completion in which case the wireless device may perform BWP switching to a BWP indicated by the PDCCH. In an example, upon/in response to reception of the PDCCH for BWP switching other than successful contention resolution, if the MAC entity decides to perform BWP switching, the MAC entity may stop the ongoing Random Access procedure and may initiate a Random Access procedure on the new activated BWP; if the MAC decides to ignore the PDCCH for BWP switching, the MAC entity may continue with the ongoing Random Access procedure on the active BWP.

In an example, if the bwp-InactivityTimer is configured, if the defaultDownlinkBWP is configured, and the active DL BWP is not the BWP indicated by the defaultDownlinkBWP; or if the defaultDownlinkBWP is not configured, and the active DL BWP is not the initialDownlinkBWP, if a PDCCH addressed to C-RNTI or CS-RNTI indicating downlink assignment or uplink grant is received on the active BWP; or if a PDCCH addressed to C-RNTI or CS-RNTI indicating downlink assignment or uplink grant is received for the active BWP; or if a MAC PDU is transmitted in a configured uplink grant or received in a configured downlink assignment: if there is no ongoing random access procedure associated with this Serving Cell; or if the ongoing Random Access procedure associated with this Serving Cell is successfully completed upon reception of this PDCCH addressed to C-RNTI, the MAC entity may for each activated Serving Cell may start or restart the bwp-InactivityTimer associated with the active DL BWP.

In an example, if the bwp-InactivityTimer is configured, if the defaultDownlinkBWP is configured, and the active DL BWP is not the BWP indicated by the defaultDownlinkBWP; or if the defaultDownlinkBWP is not configured, and the active DL BWP is not the initialDownlinkBWP, if a PDCCH for BWP switching is received on the active DL BWP, and the MAC entity switches the active BWP, the MAC entity may for each activated Serving Cell may start or restart the bwp-InactivityTimer associated with the active DL BWP.

In an example, if the bwp-InactivityTimer is configured, if the defaultDownlinkBWP is configured, and the active DL BWP is not the BWP indicated by the defaultDownlinkBWP; or if the defaultDownlinkBWP is not configured, and the active DL BWP is not the initialDownlinkBWP, if Random Access procedure is initiated on this Serving Cell, the MAC entity may for each activated Serving Cell may stop the bwp-InactivityTimer associated with the active DL BWP of this Serving Cell, if running. In an example, if the Serving Cell is SCell, the MAC entity may stop the bwp-InactivityTimer associated with the active DL BWP of SpCell, if running.

In an example, if the bwp-InactivityTimer is configured, if the defaultDownlinkBWP is configured, and the active DL BWP is not the BWP indicated by the defaultDownlinkBWP; or if the defaultDownlinkBWP is not configured, and the active DL BWP is not the initialDownlinkBWP, if the bwp-InactivityTimer associated with the active DL BWP expires, if the defaultDownlinkBWP is configured, the MAC entity may perform BWP switching to a BWP indicated by the defaultDownlinkBWP, otherwise the MAC entity may perform BWP switching to the initialDownlinkBWP.

In an example, a wireless device configured for operation in bandwidth parts (BWPs) of a serving cell, may be configured by higher layers for the serving cell a set of at most X (e.g., four) bandwidth parts (BWPs) for receptions by the wireless device (DL BWP set) in a DL bandwidth by a parameter (e.g., BWP-Downlink) and a set of at most Y (e.g., four) BWPs for transmissions by the wireless device (UL BWP set) in an UL bandwidth by a parameter (e.g., BWP-Uplink) for the serving cell.

An initial active DL BWP may be defined by a location and number of contiguous PRBs, a subcarrier spacing, and a cyclic prefix, for the control resource set for Type0-PDCCH common search space. For operation on the primary cell or on a secondary cell, a wireless device may be provided an initial active UL BWP by higher layer parameter initialuplinkBWP. If the wireless device is configured with a supplementary carrier, the wireless device may be provided an initial UL BWP on the supplementary carrier by higher layer parameter (e.g., initialUplinkBWP) in supplementaryUplink.

In an example, if a wireless device has dedicated BWP configuration, the wireless device may be provided by a higher layer parameter (e.g., firstActiveDownlinkBWP-Id) a first active DL BWP for receptions and by a higher layer parameter (e.g., firstActiveUplinkBWP-Id) a first active UL BWP for transmissions on the primary cell.

In an example, for each DL BWP or UL BWP in a set of DL BWPs or UL BWPs, respectively, the wireless device may be configured the following parameters for the serving cell: a subcarrier spacing provided by a higher layer parameter (e.g., subcarrierSpacing); a cyclic prefix provided by a higher layer parameter (e.g., cyclicPrefix); a first PRB and a number of contiguous PRBs indicated by a higher layer parameter (e.g., locationAndBandwidth) that is interpreted as RIV, setting N_(BWP) ^(size)=275, and the first PRB is a PRB offset relative to the PRB indicated by higher layer parameters (e.g., offsetToCarrier and subcarrierSpacing); an index in the set of DL BWPs or UL BWPs by respective a higher layer parameter (e.g., bwp-Id); a set of BWP-common and a set of BWP-dedicated parameters by higher layer parameters (e.g., bwp-Common and bwp-Dedicated).

In an example, for unpaired spectrum operation, a DL BWP from the set of configured DL BWPs with index provided by higher layer parameter (e.g., bwp-Id) for the DL BWP is linked with an UL BWP from the set of configured UL BWPs with index provided by higher layer parameter (e.g., bwp-Id) for the UL BWP when the DL BWP index and the UL BWP index are equal. In an example, for unpaired spectrum operation, a wireless device may not expect to receive a configuration where the center frequency for a DL BWP is different than the center frequency for an UL BWP when the bwp-Id of the DL BWP is equal to the bwp-Id of the UL BWP.

In an example, for each DL BWP in a set of DL BWPs on the primary cell, a wireless device may be configured control resource sets for every type of common search space and for wireless device-specific search space. In an example, the wireless device may not expect to be configured without a common search space on the PCell, or on the PSCell, in the active DL BWP.

In an example, for each UL BWP in a set of UL BWPs, the wireless device may be configured resource sets for PUCCH transmissions.

In an example, a wireless device may receive PDCCH and PDSCH in a DL BWP according to a configured subcarrier spacing and CP length for the DL BWP. A wireless device may transmit PUCCH and PUSCH in an UL BWP according to a configured subcarrier spacing and CP length for the UL BWP.

In an example, if a bandwidth part indicator field is configured in DCI format 1_1, the bandwidth part indicator field value may indicate the active DL BWP, from the configured DL BWP set, for DL receptions. In an example, if a bandwidth part indicator field is configured in DCI format 0_1, the bandwidth part indicator field value may indicate the active UL BWP, from the configured UL BWP set, for UL transmissions.

If a bandwidth part indicator field is configured in DCI format 0_1 or DCI format 1_1 and indicates an UL BWP or a DL BWP different from the active UL BWP or DL BWP, respectively, for each information field in the received DCI format 0_1 or DCI format 1_1, in an example, if the size of the information field is smaller than the one required for the DCI format 0_1 or DCI format 1_1 interpretation for the UL BWP or DL BWP that is indicated by the bandwidth part indicator, respectively, the wireless device may prepend zeros to the information field until its size is the one required for the interpretation of the information field for the UL BWP or DL BWP prior to interpreting the DCI format 0_1 or DCI format 1_1 information fields, respectively. In an example, if the size of the information field is larger than the one required for the DCI format 0_1 or DCI format 1_1 interpretation for the UL BWP or DL BWP that is indicated by the bandwidth part indicator, respectively, the wireless device may use a number of least significant bits of DCI format 0_1 or DCI format 1_1 equal to the one required for the UL BWP or DL BWP indicated by bandwidth part indicator prior to interpreting the DCI format 0_1 or DCI format 1_1 information fields, respectively. In an example, the wireless device may set the active UL BWP or DL BWP to the UL BWP or DL BWP indicated by the bandwidth part indicator in the DCI format 0_1 or DCI format 1_1, respectively.

In an example, a wireless device may expect to detect a DCI format 0_1 indicating active UL BWP change, or a DCI format 1_1 indicating active DL BWP change, if a corresponding PDCCH is received within the first X (e.g., 3) symbols of a slot.

In an example, for the primary cell, a wireless device may be provided by a higher layer parameter (e.g., defaultDownlinkBWP-Id) a default DL BWP among the configured DL BWPs. In an example, if a wireless device is not provided a default DL BWP by higher layer parameter defaultDownlinkBWP-Id, the default DL BWP may be the initial active DL BWP.

In an example, if a wireless device is configured for a secondary cell with higher layer parameter defaultDownlinkBWP-Id indicating a default DL BWP among the configured DL BWPs and the wireless device is configured with higher layer parameter bwp-InactivityTimer indicating a timer value, the wireless device procedures on the secondary cell may be same as on the primary cell using the timer value for the secondary cell and the default DL BWP for the secondary cell.

In an example, if a wireless device is configured by higher layer parameter bwp-InactivityTimer a timer value for the primary cell and the timer is running, the wireless device may increment the timer every interval of 1 millisecond for frequency range 1 or every 0.5 milliseconds for frequency range 2 if the wireless device does not detect a DCI format for PDSCH reception on the primary cell for paired spectrum operation or if the wireless device does not detect a DCI format for PDSCH reception or a DCI format for PUSCH transmission on the primary cell for unpaired spectrum operation during the interval.

In an example, if a wireless device is configured by higher layer parameter BWP-InactivityTimer a timer value for a secondary cell and the timer is running, the wireless device may increment the timer every interval of 1 millisecond for frequency range 1 or every 0.5 milliseconds for frequency range 2 if the wireless device does not detect a DCI format for PDSCH reception on the secondary cell for paired spectrum operation or if the wireless device does not detect a DCI format for PDSCH reception or a DCI format for PUSCH transmission on the secondary cell for unpaired spectrum operation during the interval. In an example, the wireless device may deactivate the secondary cell when the timer expires.

In an example, if a wireless device is configured by higher layer parameter firstActiveDownlinkBWP-Id a first active DL BWP and by higher layer parameter firstActiveUplinkBWP-Id a first active UL BWP on a secondary cell or supplementary carrier, the wireless device uses the indicated DL BWP and the indicated UL BWP on the secondary cell as the respective first active DL BWP and first active UL BWP on the secondary cell or supplementary carrier.

In an example, for paired spectrum operation, a wireless device does not expect to transmit HARQ-ACK information on a PUCCH resource indicated by a DCI format 1_0 or a DCI format 1_1 if the wireless device changes its active UL BWP on the PCell between a time of a detection of the DCI format 1_0 or the DCI format 1_1 and a time of a corresponding HARQ-ACK information transmission on the PUCCH.

In an example, a wireless device may not expect to monitor PDCCH when the wireless device performs RRM over a bandwidth that is not within the active DL BWP for the wireless device.

In an example, a BWP IE may be used to configure a bandwidth part. In an example, for each serving cell the network may configure at least an initial bandwidth part comprising of at least a downlink bandwidth part and one (if the serving cell is configured with an uplink) or two (if using supplementary uplink (SUL)) uplink bandwidth parts. Furthermore, the network may configure additional uplink and downlink bandwidth parts for a serving cell.

In an example, the bandwidth part configuration may be split into uplink and downlink parameters and into common and dedicated parameters. Common parameters (in BWP-UplinkCommon and BWP-DownlinkCommon) may be “cell specific” and the network ensures the necessary alignment with corresponding parameters of other wireless devices. The common parameters of the initial bandwidth part of the PCell may be provided via system information. In an example, the network may provide the common parameters via dedicated signaling. Example BWP IE is shown below:

BWP ::= SEQUENCE {  locationAndBandwidth  INTEGER (0..37949),  subcarrierSpacing  SubcarrierSpacing,  cyclicPrefix  ENUMERATED { extended }    OPTIONAL  -- Need R } BWP-Uplink ::=  SEQUENCE {  bwp-Id  BWP-Id,  bwp-Common   BWP-UplinkCommon     OPTIONAL,  -- Need M  bwp-Dedicated  BWP-UplinkDedicated   OPTIONAL, -- Need M  ... } BWP-UplinkCommon ::=  SEQUENCE {  genericParameters  BWP,  rach-ConfigCommon   SetupRelease { RACH-ConfigCommon }     OPTIONAL,   -- Need M  pusch-ConfigCommon   SetupRelease { PUSCH-ConfigCommon }     OPTIONAL,   -- Need M  pucch-ConfigCommon   SetupRelease { PUCCH-ConfigCommon }     OPTIONAL,   -- Need M  ... } BWP-UplinkDedicated ::= SEQUENCE {  pucch-Config  SetupRelease { PUCCH-Config }   OPTIONAL,  -- Need M  pusch-Config  SetupRelease { PUSCH-Config }   OPTIONAL,  -- Cond SetupOnly  configuredGrantConfig  SetupRelease { ConfiguredGrantConfig }   OPTIONAL, -- Need M  srs-Config  SetupRelease { SRS-Config }   OPTIONAL,  -- Need M  beamFailureRecoveryConfig   SetupRelease { BeamFailureRecoveryConfig }    OPTIONAL,  -- Cond SpCellOnly  ... } BWP-Downlink ::=  SEQUENCE {  bwp-Id  BWP-Id,  bwp-Common   BWP-DownlinkCommon     OPTIONAL,   -- Need M  bwp-Dedicated  BWP-DownlinkDedicated   OPTIONAL, -- Need M  ... } BWP-DownlinkCommon ::=   SEQUENCE {  genericParameters  BWP,  pdcch-ConfigCommon   SetupRelease { PDCCH-ConfigCommon }     OPTIONAL,   -- Need M  pdsch-ConfigCommon   SetupRelease { PDSCH-ConfigCommon }     OPTIONAL,   -- Need M  ... } BWP-DownlinkDedicated ::=  SEQUENCE {  pdcch-Config  SetupRelease { PDCCH-Config }   OPTIONAL, -- Need M  pdsch-Config  SetupRelease { PDSCH-Config }   OPTIONAL, -- Need M  sps-Config  SetupRelease { SPS-Config }   OPTIONAL, -- Need M  radioLinkMonitoringConfig   SetupRelease { RadioLinkMonitoringConfig }    OPTIONAL,  -- Need M  ... }

In an example, cyclic prefix may indicate whether to use the extended cyclic prefix for this bandwidth part. If not set, the wireless device may use the normal cyclic prefix. Normal CP may be supported for all numerologies and slot formats. Extended CP may be supported only for 60 kHz subcarrier spacing. In an example, locationAndBanddwidth may indicate frequency domain location and bandwidth of this bandwidth part. The value of the field may be interpreted as resource indicator value (RIV). The first PRB may be a PRB determined by subcarrierSpacing of this BWP and offsetToCarrier (configured in SCS-SpecificCarrier contained within FrequencylnfoDL) corresponding to this subcarrier spacing. In case of TDD, a BWP-pair (UL BWP and DL BWP with the same bwp-Id) may have the same center frequency. In an example, subcarrierSpacing may indicate subcarrier spacing to be used in this BWP for all channels and reference signals unless explicitly configured elsewhere. In an example, the value kHz15 may corresponds to μ=0, kHz30 to μ=1, and so on. In an example, the values 15, 30, or 60 kHz may be used. In an example, bwp-Id may indicate an identifier for this bandwidth part. Other parts of the RRC configuration may use the BWP-Id to associate themselves with a particular bandwidth part. The BWP ID=0 may be associated with the initial BWP and may hence not be used here (in other bandwidth parts). The NW may trigger the wireless device to switch UL or DL BWP using a DCI field. The four code points in that DCI field may map to the RRC-configured BWP-ID as follows: For up to 3 configured BWPs (in addition to the initial BWP) the DCI code point may be equivalent to the BWP ID (initial=0, first dedicated=1, . . . ). If the NW configures 4 dedicated bandwidth parts, they may be identified by DCI code points 0 to 3. In this case it is not possible to switch to the initial BWP using the DCI field. In an example, bwp-Id may indicate an identifier for this bandwidth part. Other parts of the RRC configuration may use the BWP-Id to associate themselves with a particular bandwidth part. The BWP ID=0 may be associated with the initial BWP and may hence may not be used here (in other bandwidth parts). The NW may trigger the wireless device to switch UL or DL BWP using a DCI field. The four code points in that DCI field map to the RRC-configured BWP-ID as follows: For up to 3 configured BWPs (in addition to the initial BWP) the DCI code point may be equivalent to the BWP ID (initial=0, first dedicated=1, . . . ). If the NW configures 4 dedicated bandwidth parts, they may be identified by DCI code points 0 to 3. In this case it may not be possible to switch to the initial BWP using the DCI field. In an example, rach-ConfigCommon may indicate configuration of cell specific random access parameters which the wireless device may use for contention based and contention free random access as well as for contention based beam failure recovery. In an example, the NW may configure SSB-based RA (and hence RACH-ConfigCommon) only for UL BWPs if the linked DL BWPs allows the wireless device to acquire the SSB associated to the serving cell. In an example, PUCCH-config may indicate PUCCH configuration for one BWP of the regular UL or SUL of a serving cell. If the wireless device is configured with SUL, the network may configure PUCCH only on the BWPs of one of the uplinks (UL or SUL).

In an example, the network may configure PUCCH-Config for each SpCell. If supported by the wireless device, the network may configure at most one additional SCell of a cell group with PUCCH-Config (i.e. PUCCH SCell). In an example, the IE BWP-Id may be used to refer to Bandwidth Parts (BWP). The initial BWP is referred to by BWP-Id 0. The other BWPs are referred to by BWP-Id 1 to maxNrofBWPs. In an example, the ServingCellConfig IE may be used to configure (add or modify) the wireless device with a serving cell, which may be the SpCell or an SCell of an MCG or SCG. In an example, the parameters may be mostly wireless device specific but partly also cell specific (e.g. in additionally configured bandwidth parts). An example, ServingCellConfig IE is shown below:

ServingCellConfig ::=  SEQUENCE {  tdd-UL-DL-ConfigurationDedicated TDD-UL-DL-ConfigDedicated  OPTIONAL,   -- Cond TDD  initialDownlinkBWP BWP-DownlinkDedicated  OPTIONAL,   -- Cond ServCellAdd  downlinkBWP-ToReleaseList SEQUENCE (SIZE (1..maxNrofBWPs)) OF BWP- Id OPTIONAL,  -- Need N  downlinkBWP-ToAddModList SEQUENCE (SIZE (1..maxNrofBWPs)) OF BWP- Downlink OPTIONAL,  -- Need N  firstActiveDownlinkBWP-Id BWP-Id  OPTIONAL,   -- Cond SyncAndCellAdd  bwp-InactivityTimer ENUMERATED { ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30,   ms40,ms50, ms60, ms80, ms100, ms200, ms300, ms500,   ms750, ms1280, ms1920, ms2560, spare10, spare9, spare8,   spare7, spare6, spare5, spare4, spare3, spare2, spare1 } OPTIONAL,  -- Need R  defaultDownlinkBWP-Id BWP-Id  OPTIONAL,   -- Need S  uplinkConfig   UplinkConfig     OPTIONAL, -- Cond ServCellAdd-UL  supplementaryUplink UplinkConfig OPTIONAL,  -- Cond ServCellAdd-SUL  pdcch-ServingCellConfig SetupRelease { PDCCH-ServingCellConfig }  OPTIONAL,   -- Need M  pdsch-ServingCellConfig SetupRelease { PDSCH-ServingCellConfig }  OPTIONAL,   -- Need M  csi-MeasConfig   SetupRelease { CSI-MeasConfig } OPTIONAL,  -- Need M  sCellDeactivationTimer ENUMERATED { ms20, ms40, ms80, ms160, ms200, ms240,   ms320, ms400, ms480, ms520, ms640, ms720,   ms840, ms1280, spare2,spare1}   OPTIONAL,  -- Cond ServingCellWithoutPUCCH  crossCarrierSchedulingConfig   CrossCarrierSchedulingConfig     OPTIONAL, -- Need M  tag-id   TAG-Id,  ue-BeamLockFunction ENUMERATED {enabled}   OPTIONAL, -- Need R  pathlossReferenceLinking   ENUMERATED {pCell, sCell}  OPTIONAL,   -- Cond SCellOnly  servingCellMO   MeasObjectId     OPTIONAL, -- Cond MeasObject  ... } UplinkConfig ::=  SEQUENCE {  initialUplinkBWP   BWP-UplinkDedicated OPTIONAL,  -- Cond ServCellAdd  uplinkBWP-ToReleaseList SEQUENCE (SIZE (1..maxNrofBWPs)) OF BWP- Id OPTIONAL,   -- Need N  uplinkBWP-ToAddModList  SEQUENCE (SIZE (1..maxNrofBWPs)) OF BWP-Uplink   OPTIONAL,    -- Need N  firstActiveUplinkBWP-Id BWP-Id  OPTIONAL,   -- Cond SyncAndCellAdd  pusch-ServingCellConfig SetupRelease { PUSCH-ServingCellConfig }  OPTIONAL,   -- Need M  carrierSwitching   SetupRelease { SRS-CarrierSwitching } OPTIONAL,  -- Need M  ... }

In an example, the bwp InactivityTimer may have a duration in ms after which the wireless device may fall back to the default Bandwidth Part. In an example, the value 0.5 ms may be applicable for carriers >6 GHz. In an example, when the network releases the timer configuration, the wireless device may stop the timer without switching to the default BWP.

In an example, defaultDownlinkBWP-Id may correspond to L1 parameter ‘default-DL-BWP’. The initial bandwidth part may be referred to by BWP-Id=0. ID of the downlink bandwidth part to be used upon expiry. This field may be wireless device specific. When the field is absent the wireless device may use the initial BWP as default BWP.

In an example, downlinkBWP-ToAddModList may indicate list of additional downlink bandwidth parts to be added or modified.

In an example, downlinkBWP-ToReleaseList may indicate list of additional downlink bandwidth parts to be released.

In an example, firstActiveDownlinkBWP-Id if configured for an SpCell, may contain the ID of the DL BWP to be activated upon performing the reconfiguration in which it is received. If the field is absent, the RRC reconfiguration may not impose a BWP switch (corresponds to L1 parameter ‘active-BWP-DL-Pcell’). If configured for an SCell, this field may contain the ID of the downlink bandwidth part to be used upon MAC-activation of an SCell. The initial bandwidth part may be referred to by BWP-Id=0.

In an example, initialDownlinkBWP may indicate a dedicated (UE-specific) configuration for the initial downlink bandwidth-part. In an example, firstActiveUplinkBWP-Id if configured for an SpCell, may contains the ID of the DL BWP to be activated upon performing the reconfiguration in which it is received. If the field is absent, the RRC reconfiguration may not impose a BWP switch (corresponds to L1 parameter ‘active-BWP-UL-Pcell’). If configured for an SCell, this field may contain the ID of the uplink bandwidth part to be used upon MAC-activation of an SCell. The initial bandwidth part may be referred to by BandiwdthPartId=0. In an example, initialUplinkBWP may indicate a dedicated (UE-specific) configuration for the initial uplink bandwidth-part.

In an unlicensed band, a type of LBT (CAT1, CAT2, CAT3, and/or CAT4) may be configured via control messages (RRC, MAC CE, and/or DCI) per a cell. In an example, a type of LBT (CAT1, CAT2, CAT3, and/or CAT4) may be configured via control messages (RRC, MAC CE, and/or DCI) per BWP. For example, a type of LBT (CAT1, CAT2, CAT3, and/or CAT4) may be determined at least based on a numerology configured in a BWP. In this case, BWP switching may change a type of LBT.

In an example, a base station may configure a wireless device with one or more UL carriers associated with one DL carrier of a cell. One of one or more UL carriers configured with a DL carrier may be referred to as a supplementary uplink (SUL) carrier or a normal UL (NUL or may be referred to as a non-SUL) carrier. In an example, a base station may enhance UL coverage and/or capacity by configuring an SUL carrier. A base station may configure a BWP configuration per an uplink (e.g., per uplink carrier) in a cell. For example, a base station may configure one or more BWPs on an SUL separately from one or more BWPs on a NUL. A base station may control an active BWP of an SUL independently of an active BWP of a NUL. For example, a base station may control two uplink transmissions on two ULs (e.g., NUL and SUL) to avoid overlapping PUSCH transmissions in time.

In an example, a base station may avoid configuring parallel uplink transmissions via SUL and NUL of a cell, wherein the parallel uplink transmissions may be PUCCH (and/or PUSCH) via SUL and PUCCH (and/or PUSCH) via NUL. In an example, a base station may transmit one or more RRC message (e.g., wireless device specific RRC signaling) to (re-) configure a location of a PUCCH on an SUL carrier and/or on a NUL carrier. A base station may transmit, to a wireless device, one or more RRC messages comprising configuration parameters for a carrier, wherein the configuration parameters may indicate at least one of random access procedure configuration, BWP configurations (e.g., number of DL/UL BWPs, bandwidth and/or index of configured DL/UL BWP, and/or initial, default, and/or active DL/UL BWP), PUSCH configurations, PUCCH configurations, SRS configurations, and/or a power control parameters.

In an example, a base station may configure an SUL carrier and a NUL carrier to support a random access procedure (e.g., initial access). For example, as shown in FIG. 12, to support a random access to a cell configured with SUL, a base station may configure a RACH configuration 1210 of SUL independent of a RACH configuration 1210 of NUL. For example, one or more parameters associated with Msg 1 1220, Msg 2 1230, Msg 3 1240, and/or contention resolution 1250 via SUL may be configured independent of one or more parameters associated with Msg 1 1220, Msg 2 1230, Msg 3 1240, and/or contention resolution 1250 via NUL. For example, one or more parameters associated with PRACH transmissions in Msg 1 1220 via SUL may be independent of one or more parameters associated with PRACH transmission via NUL.

For a random access procedure in licensed bands, based on a measurement (e.g., RSRP) of one or more DL pathloss references, a wireless device may determine which carrier (e.g., between NUL and SUL) to use. For example, a wireless device may select a first carrier (e.g., SUL or NUL carrier) if a measured quality (e.g., RSRP) of DL pathloss references is lower than a broadcast threshold (e.g., an RRC parameter, rsrp-ThresholdSSB-SUL in FIG. 18). If a wireless device selects a carrier between SUL carrier and NUL carrier for a random access procedure, one or more uplink transmissions associated with the random access procedure may remain on the selected carrier.

In an example, a base station may configure NUL and SUL with a TAG. For example, for an uplink transmission of a first carrier (e.g., SUL) of a cell, a wireless device may employ a TA value received during a random access procedure via a second carrier (e.g., NUL) of the cell.

FIG. 24 is an example of a coverage of a cell configured with a DL and two ULs. For example, a base station may configure a NUL and DL over a first frequency (e.g., high frequency). An SUL may be configured over a second frequency (e.g., low frequency) to support uplink transmission (e.g., in terms of coverage and/or capacity) of a cell. In an example, a broadcast threshold (e.g., an RRC parameter, rsrp-ThresholdSSB-SUL) for a wireless device to select a carrier may be determined such that a wireless device located outside a NUL coverage 2410 but inside an SUL coverage 2420 may start a random access procedure via an SUL. A wireless device located inside a NUL coverage 2410 may start a random access procedure via a NUL. A wireless device may employ a RACH configuration associated with a selected carrier for a random access procedure.

In an example, a wireless device may perform a contention based random access procedure and/or a contention free random access procedure. In an example, a wireless device may perform a random access procedure on an UL selected based on a broadcast threshold (e.g., rsrp-ThresholdSSB-SUL). For example, this is a case when a base station does not indicate (e.g., explicitly) the wireless device which carrier to start a random access procedure. In an example, a base station may indicate which carrier a wireless device performs a random access procedure by transmitting a RACH configuration with an SUL indicator (e.g., 0 may indicates a NUL carrier, 1 may indicate an SUL carrier or vice versa). In an example, a base station may indicate (e.g., explicitly) to a wireless device which UL carrier to be employed for a contention free or contention based random access procedure. In an example, a base station may indicate a contention free random access procedure by transmitting a RACH configuration with a dedicated preamble index. In an example, a base station may indicate a contention based random access procedure by transmitting a RACH configuration without a dedicated preamble index.

In an example, it may be beneficial for a network to receive one or more measurements of NUL carrier(s) and/or SUL carrier(s) to initiate a (contention free or contention based) random access procedure for a wireless device. For example, a base station may configure a wireless device (e.g., a wireless device in RRC Connected) with one or more measurements on one or more DL reference signals associated with NUL carrier(s) and/or SUL carrier(s) of a cell.

For example, if a wireless device transmits quality information of one or more measurements on one or more DL reference signals associated with NUL carrier(s) and/or SUL carrier(s), a base station may select a carrier between NUL carrier(s) and/or SUL carrier(s) based on the quality of the one or more measurements. A base station may indicate, to a wireless device, a selected carrier via RRC signaling (e.g., handover) and/or PDCCH order (e.g., SCell addition) for initiating a (contention free or contention based) random access procedure. In an example, e.g., for load balancing between NUL carrier(s) and/or SUL carrier(s), a base station may select one of NUL and SUL carrier by taking into consideration congestion in NUL carrier(s) and/or SUL carrier(s). For example, based on one or more measurement reports associated with NUL carrier(s) and/or SUL carrier(s), a base station may better select a carrier (e.g., NUL or SUL) of a target cell for a (contention free or contention based) random access procedure for a handover. For example, based on one or more measurement reports associated with NUL carrier(s) and/or SUL carrier(s), a base station may better select a carrier (e.g., NUL or SUL) of an SCell (e.g., when the SCell is configured with at least a NUL carrier and an SUL carrier) for a (contention free or contention based) random access procedure for an SCell addition.

In an example, for a handover of a wireless device, a source base station may make a decision on a handover to one or more target cells. A source base station may indicate a handover decision to a target base station associated with one or more target cells that the source base station selects. A target base station may indicate to a wireless device (e.g., through a cell of a source gNB) which carrier (between NUL carrier(s) and SUL carrier(s)) to use via a handover command. For example, a handover command received by a wireless device may comprise an SUL indicator (e.g., 1 bit) along with one or more RACH parameters (e.g., dedicated preamble index, and/or PRACH mask index), wherein the SUL indicator may indicate if the one or more RACH parameters are associated with an SUL or NUL carrier.

For example, it may be useful that a source base station informs a target base station about measured results on NUL carrier(s) and SUL carrier(s), e.g., high frequency carrier(s) and low frequency carrier(s), so that the target base station determines a carrier on which a wireless device may perform a (contention free or contention based) random access procedure for a handover. In an example, when a source base station configures DL measurements on one or more cells association with a NUL carrier(s) and/or SUL carrier(s) of a target gNB, the source base station may need to know whether SUL carrier(s) is (are) configured in the target gNB, and/or which carrier is allowed to be employed for a handover. For example, a target base station may inform a source base station of one or more configurations of NUL carrier(s) and/or SUL carrier(s) of one or more cells in the target gNB. A source base station may configure DL measurement on one or more cells in the target gNB, based on one or more configurations indicating carrier configurations at the one or more cells in the target gNB.

In an example, for an SCell addition, a base station may be aware of whether SUL carrier(s) is (are) configured in an SCell, and/or which carrier is allowed to be employed for an SCell addition. A base station may configure DL measurements on NUL carrier(s) and/or SUL carrier(s). A base station may configure a wireless device with one or more RACH configurations for an SCell, e.g., a first RACH configuration for an SUL carrier, a second RACH configuration for a NUL carrier, and so on. A base station may transmit, to a wireless device via a PDCCH order comprising a parameter indicating in which carrier the wireless device starts a (contention free or contention based) random access procedure. For example, a PDCCH order triggering a (contention free or contention based) random access procedure may comprise one or more parameters indicating at least one of at least one preamble (e.g., preamble index), one or more PRACH resources (e.g., PRACH mask index), an SUL indicator, and/or a BWP indicator. For example, for an random access procedure, a wireless device receiving a PDCCH order may transmit at least one preamble via one or more PRACH resources of a BWP indicated by a BWP indicator of a carrier indicated by an SUL indicator.

In an example, a wireless device may determine a random access procedure unsuccessfully completed. For example, if a wireless device receives no RAR corresponding to one or more preambles transmitted by the wireless device during a random access procedure, the wireless device may consider the random access procedure unsuccessfully completed. There may be a number of preamble transmissions allowed during a random access procedure (e.g., preambleTransMax in FIG. 20), wherein the number of preamble transmissions may be semi-statically configured by RRC. For example, if a wireless device receives no RAR corresponding to the number of preamble transmissions, the wireless device may consider a random access procedure unsuccessfully completed. In response to an unsuccessful completion of a random access procedure, a wireless device may indicate a problem to upper layer(s), wherein, in response to the indicated problem, the upper layers(s) may trigger radio link failure that may lead to prolonged random access delay and degraded user experience.

For example, a base station (source base station and/or a target gNB) configuring a wireless device with a RACH configuration for a random access (for a handover and/or SCell addition) may not allow to reuse the RACH configuration if the random access is unsuccessfully completed.

In an example, a failure of a (contention free or contention based) random access may result in a long delay of random access. For example, if a contention free random access is unsuccessfully completed, instead of a contention free random access, a wireless device may initiate a contention based random access procedure. For example, if a wireless device fails a contention free random access to a target base station during a handover, the wireless device may perform an initial access to the target base station based on a contention based random access. A wireless device performing a contention based random access procedure may compete with one or more wireless devices to get an access to a gNB, which may not guarantee a success of the contention based random access procedure, and/or which may take long (e.g., four step procedure of the contention based random access procedure comparing with a contention free random access comprising MSG 1 1220 and MSG 2 1230 transmissions) to receive a corresponding RAR.

In an example, if a wireless device fails a contention free random access for an SCell addition, the wireless device may wait until a base station transmits a message (e.g., PDCCH order) indicating a RACH configuration, based on which the wireless device may initiate a random access for an SCell addition. It may take long for a base station to detect a failure of a random access for an SCell addition. A wireless device may wait for a message (e.g., PDCCH order) transmitted a base station for an SCell addition unnecessarily long.

In an unlicensed band, a failure of a random access may occur due to LBT. For example, in an unlicensed band, at least one LBT may be performed prior to DL and/or UL transmission. For example, in a random access procedure in FIG. 12, Msg 1 1220, Msg 2 1230, Msg 3 1240, and contention resolution 1250 may require at least one LBT before the transmission for contention based random access, e.g., at least 4 LBTs. For contention-free case, Msg 1 1220 and Msg2 1230 may require at least one LBT, e.g., at least 2 LBTs. FIG. 25 is an example diagram of contention based and contention-free random access procedures with LBT.

In an example, a base station and/or a wireless device may not transmit a message (e.g., Msg 1 2520, Msg 2 2530, Msg 3 2540, and contention resolution 2550) for a random access procedure if LBT is failed prior to transmitting the message, e.g., CCA in LBT determines that a channel in unlicensed band is busy (occupied by other device). In an example, a failure of LBT may result in degrading a user experience (e.g., in terms of QoS, capacity (throughput), and/or coverage). For example, a base station and/or a wireless device may wait until the channel becomes idle. This may result in a latency problem to make a radio link connection between a base station and a wireless device. For example, a failure of an LBT during a random access procedure may lead a long delay for a wireless device to receive an UL grant and/or TA value from a base station. This may result in a call drop and/or traffic congestion. For example, a failure of an LBT in a random access procedure for an SCell addition may lead a cell congestion (e.g., load imbalancing) on one or more existing cells, e.g., since an SCell may not take over traffic from the one or more existing cells in time.

In an example, there may be a need to improve an efficiency of random access procedure operating in unlicensed band, e.g., to compensate a latency/delay, and/or performance degradation, due to the LBT failure. For example, selecting two or more SSBs and performing one or more LBTs on one or more PRACH occasions associated with the two or more SSBs my increase a success rate of LBT. For example, a wireless device may measure a plurality of downlink reference signals (SSBs or CSI-RS s, if CSI-RS is configured by RRC). The wireless device may select two or more SSBs by comparing RSRPs of the plurality of downlink reference signals and a threshold. For example, the threshold may comprise rsrp-ThresholdSSB when the plurality of downlink reference signals are SSBs. For example, the threshold may comprise rsrp-ThresholdCSl-RS when the plurality of downlink reference signals are CSI-RS s. For example, the wireless device may select two or more downlink referencing signals (SSBs or CSI-RS s) whose RSRPs are higher than the threshold. For example, if SSBs are configured with the wireless device, the wireless device may determine one or more PRACH occasions associated with the selected two or more downlink reference signals, e.g., SSBs. For example, the wireless device may determine the one or more PRACH based on an association between PRACH occasions and SSBs that may be indicated by one or more RRC parameters, e.g., ra-ssb-OccasionMaskIndex. For example, if CSI-RS s are configured with the wireless device, the wireless device may determine one or more PRACH occasions associated with the selected two or more downlink reference signals, e.g., CSI-RS s. For example, the wireless device may determine the one or more PRACH based on an association between PRACH occasions and CSI-RS s that may be indicated by one or more RRC parameters, e.g., ra-OccasionList.

In an example, a two-step RA procedure may employ LBT in an unlicensed band. FIG. 26 is an example diagram of a two-step RA procedure with LBT. A base station and/or a wireless device may not transmit a message (e.g., two-step Msg 1 2610, preamble 2630, one or more transport blocks 2640, and/or two-step Msg 2 2650) for a random access procedure if LBT is failed prior to transmitting the message, e.g., CCA in LBT determines that a channel in unlicensed band is busy (occupied by other device). The transmissions of Preamble 2630 and for one or more transport blocks 2640 may have a same LBT and/or different LBTs.

For example, radio resources for transmissions of Preamble 2630 and one or more transport blocks 2640 may be configured in a same channel (or a same subband or a same BWP or a same UL carrier), where a wireless device performs an LBT for the transmissions (e.g., based on a regulation). In this case, an LBT result on the same channel (or the same subband or the same BWP or the same UL carrier) may applied for transmissions of Preamble 2630 and for one or more transport blocks 2640. For example, FIG. 27 is an example of radio resource allocation for a two-step RA procedure. If a frequency offset in FIG. 27 is zero, PRACH 2730 and UL radio resources 2740 may be time-multiplexed. If a time offset in FIG. 27 is zero, PRACH 2730 and UL radio resources 2740 may be frequency-multiplexed. The frequency offset in FIG. 27 may be an absolute number in terms of Hz, MHz, and GHz, and/or a relative number, e.g., one of frequency indices predefined/preconfigured. The time offset in FIG. 27 may be an absolute number in terms of micro-second, milli-second, or second and/or a relative number, e.g., in terms of subframe, slot, mini-slot, OFDM symbol. PRACH 2730 for transmission of preamble 2630 and UL radio resources for transmission of one or more TB s 2640 may be subject to one LBT if f1 2710 and f2 2720 are configured in the same channel (or a same subband or a same BWP or a same UL carrier). For example, in FIG. 27, one LBT before PRACH 2730 may be performed by a wireless device (e.g., based on a regulation of unlicensed band). For example, a number of LBTs may be determined based on a value of time offset in FIG. 27. For example, one LBT before PRACH 2730 may be performed by a wireless device if the value of time offset is equal to and/or less than a threshold (that may be configured and/or defined by a regulation). For example, the one LBT determines idle, a wireless device may perform a transmission of Preamble 2630 via PRACH 2730 followed by a second transmission of one or more TBs 2640 via the UL radio resources 2740 with no LBT (the transmission order may be switched if the UL radio resources 2740 is allocated before PRACH 2730 in time domain). This may be a case that PRACH and UL radio resources are allocated closely enough in time domain. For example, if the value of time offset is larger than the threshold, a wireless device may perform a first LBT before PRACH 2730 and perform a second LBT before Ul radio resources 2740.

For example, a bandwidth of BWP and/or UL carrier is larger than a first value (e.g., 20 MHz) and f1 2710 and f2 2720 are configured in the bandwidth, a wireless may perform an LBT and apply a result (idle/busy) of the LBT to the transmission of preamble 2630 and UL radio resources for transmission of one or more TBs 2640. For example, if the channel is idle, a wireless device may perform the transmissions of Preamble 2630 and for one or more transport blocks 2640. If the channel is busy, a wireless device may not perform the transmissions of Preamble 2630 and for one or more transport blocks 2640.

For example, a bandwidth of BWP and/or UL carrier is less than a first value (e.g., 20 MHz) and f1 2710 and f2 2720 are configured in the bandwidth, a wireless may perform an LBT and apply a result (idle/busy) of the LBT to the transmission of preamble 2630 and UL radio resources for transmission of one or more TBs 2640. For example, if the channel is idle, a wireless device may perform a first transmissions of Preamble 2630 followed by a second transmission of one or more transport blocks 2640. If the channel is busy, a wireless device may not perform the transmissions of Preamble 2630 and for one or more transport blocks 2640.

For example, radio resources for transmissions of Preamble 2630 and one or more transport blocks 2640 may be configured in different channels (or different subbands or different BWPs or different UL carriers e.g., one in NUL and the other one in SUL) that may require separate LBTs. For example, a wireless device may perform an LBT per one or more channels, per one or more subbands, per one or more BWPs, and/or per one or more UL carriers. FIG. 28 is an example of one or more LBTs performed for a two-step RA procedure. In some cases, UL radio resources 2850 may be allocated before or aligned with PRACH 2830 in time. A wireless device may perform a first LBT (e.g., LBT 2840 in FIG. 28) before a first transmission of preamble 2630 (e.g., via PRACH 2830) and perform a second LBT (e.g., LBT 2860 in FIG. 28) before a second transmission of one or more transport blocks 2640 (e.g., via UL radio resources 2850). Depending on results of the first LBT and the second LBT, a wireless device may perform none of, one of, or both of the first transmission and the second transmission.

For example, the first transmission may be performed when a first result of the first LBT is idle. The second transmission may be independent of the first result. For example, the second transmission may be performed when a second result of the second LBT is idle. In this case, there may be a case that a wireless device may transmit Preamble 2630 in response to the first LBT being idle and may not be able to transmit one or more transport blocks 2640 in response to the second LBT being busy. For example, a wireless device may not transmit Preamble 2630 in response to the first LBT being busy and may transmit one or more transport blocks 2640 in response to the second LBT being idle. In a two-step RA procedure, one or more transport blocks may comprise an identifier of the wireless device so that a base station may identify which wireless device transmit the one or more transport blocks. The identity may be configured by the base station and/or may be at least a portion of wireless device-specific information, e.g., resume ID, DMRS sequence/index, IMSI, etc. If a wireless device transmits one or more TBs with no Preamble 2630 (e.g., when a channel, e.g. PRACH 2830 is busy), a base station may identify the wireless device based on the identity in the one or more TBs.

In a two-step RA procedure configured in an unlicensed band, the separate LBTs for transmissions of Preamble and one or more TBs may be performed in one or more cases. For example, a base station may configure a wireless device with the separate LBTs for a wideband operation (e.g., for a case that a bandwidth may be larger than 20 MHz). In the wideband operation, a base station may configure a wireless device with a wideband comprising one or more subbands and/or one or more BWPs. Some of the one or more subbands may be overlapped to each other at least a portion in frequency domain. Some of the one or more subbands may not be overlapped to each other at least a portion in frequency domain. Some of the one or more BWPs may be overlapped to each other at least a portion in frequency domain. Some of the one or more BWPs may not be overlapped to each other at least a portion in frequency domain. In a wideband operation, if two radio resources are allocated with a space larger than a threshold (e.g., 20 MHz) in frequency domain, separate LBTs may be required for transmissions via the two radio resources. For example, a wideband may comprise one or more subbands, and two radio resources may be allocated in different subbands. In this case, a first transmission scheduled in a first subband requires a first LBT, and a second transmission scheduled in a second subband requires an second LBT. The first LBT and the second LBT may be independent of each other.

For example, UL radio resources for transmission of one or more TBs 2640 may be subject to a first LBT (e.g., LBT 2860) and be independent of a second LBT (e.g., LBT 2840) for transmission of Preamble 2630. For example, PRACH 2830 for transmission of Preamble 2630 may be subject to a second LBT (e.g., LBT 2860) and be independent of a first LBT (e.g., LBT 2860) for transmission of one or more TBs 2640. For example, if f1 2710 and f2 2720 are configured in different channels (or different subbands or different BWPs or different UL carriers), a wireless device may perform separate LBTs for a first transmissions of Preamble 2630 and a second transmission of one or more transport blocks 2640.

For example, FIG. 29A and FIG. 29B are examples of one or more LBTs performed for a two-step RA procedure in an unlicensed band. The resource allocation and the separate LBTs in FIG. 28 may be resulted from FIG. 29A and/or FIG. 29B. For example, a base station may configure a wireless device with one or more PRACH and one or more UL radio resources in different channels (BWPs and/or UL carriers). The wireless device may one or more first opportunities to transmit preambles and one or more second opportunities to transmit one or more TBs. For example, in FIG. 29A, a wireless device may have two opportunities in PRACH 2930 and PRACH 2830 for preamble transmission. Depending on LBT results, a wireless device may select one of two opportunities. For example, a wireless device may perform a first LBT (e.g., LBT 2940) and a second LBT (e.g., LBT 2840 in FIG. 29A). If the results of the first and second LBTs are idle, a wireless device may select one of PRACH associated either a first LBT or a second LBT (e.g., based on random selection). If one of LBT result is idle and the other of LBT result is busy, a wireless device may select PRACH associated with the LBT being idle for preamble transmission. If the first and second LBTs are busy, a wireless device may not transmit a preamble and may perform one or more LBTs for one or more TB transmissions.

A wireless device may have one or more opportunities for transmission of one or more TBs via UL radio resources (e.g., in a similar way that a wireless device has for preamble transmission above). For example, the one or more opportunities for transmission of one or more TBs may be independent of one or more opportunities for transmission of preamble. For example, if a wireless device does not transmit a preamble due to a result (busy) of LBT, the wireless device may perform one or more LBTs to gain access to a channel to transmit one or more TBs. For example, in FIG. 29A, a wireless device may have a first LBT (e.g., LBT 2920) followed by a first transmission opportunity of one or more TBs via first UL radio resources 2910 and a second LBT (e.g., LBT 2860 in FIG. 29A) followed by a second transmission opportunity of one or more TBs via second UL radio resources 2850. Depending on LBT results, a wireless device may select one of opportunities. For example, in FIG. 29A, if LBT 2920 is busy but LTB 2860 is idle, a wireless device may transmit one or more TBs via UL radio resources 2850. If one or more LBTs (e.g., LBT 2840 and LBT 2940 in FIG. 29A) to gain access for transmitting a preamble are busy, a wireless device may not transmit any preamble. In this case, a wireless device may perform one or more second LBTs (e.g., LBT 2920 and LBT 2860 in FIG. 29A) for transmission of one or more TBs.

For example, before a wireless device initiates a two-step RA procedure, the wireless device may receive, from a base station, control message(s) (e.g., RRC and/or PDCCH) indicating one or more associations between PRACH and UL radio resources. The associations may be one-to-one, multi-to-one, one-to-multi, and/or multi-to-multi between one or more PRACHs and one or more UL radio resources. Based on the associations, a wireless device may determine which UL radio resources and/or which PRACH need to be selected. For example, in FIG. 29A, the associations may indicate one-to-multi association from PRACH 2830 to UL radio resources 2850 and UL radio resources 2910. For example, the associations may indicate one-to-one association from PRACH 2930 to UL radio resources 2850. In this case, a wireless device may perform one or more LBTs (depending on a regulation and/or resource allocation whether they are in the same channel) for transmission of one or more TBs depending on a selection of PRACH. For example, in FIG. 29A, a wireless device may perform two LBTs (LBT 2840 and LBT 2940). If LBT 2840 may be idle but LBT 2940 may be busy, a wireless device transmits a preamble via PRACH 2830. The wireless device may choose one or more candidate UL radio resources based on a configured association of PRACH 2830, which may be one-to-multi from PRACH 2830 to UL radio resources 2850 and UL radio resources 2910. The wireless device may perform LBT 2960 and LBT 2860 based on the configured association. Depending on the results of the LBTs, a wireless device may transmit one or more TBs. FIG. 29B is an example of a two-step RA procedure. In this case, UL radio resources is associated with one PRACH. For example, a base station configured an association from PRACH 2830 to UL radio resource 2850 and UL radio resources 2950.

The PRACH and/or Ul radio resources in FIG. 27, FIG. 28, FIG. 29A, and/or FIG. 29B may be associated with at least one reference signal configuration (SSB, CSI-RS, DM-RS). A base station may transmit at least one control message to a wireless device to indicate such an association. If the base station transmit a plurality of reference signals, a configuration of each reference signal have an association with at least one PRACH, that may be configured by RRC and/or PDCCH. In downlink channel, there may be a plurality of PRACHs and a plurality of UL radio resources associated with the plurality of PRACHs.

In an example, a failure of LBT may result in degrading a user experience (e.g., in terms of QoS, capacity (throughput), and/or coverage). For example, a base station and/or a wireless device may wait until the channel becomes idle. This may result in a latency problem to make a radio link connection between a base station and a wireless device. For example, a failure of an LBT during a random access procedure may lead a long delay for a wireless device to receive an UL grant and/or TA value from a base station. This may result in a call drop and/or traffic congestion. For example, a failure of an LBT in a random access procedure for an SCell addition may lead a cell congestion (e.g., load imbalancing) on one or more existing cells, e.g., since an SCell may not take over traffic from the one or more existing cells in time.

In an example, there may be a need to improve an efficiency of random access procedure operating in unlicensed band, e.g., to compensate a latency/delay, and/or performance degradation, due to the LBT failure. For example, selecting two or more SSBs and performing one or more LBTs on one or more PRACH occasions associated with the two or more SSBs my increase a success rate of LBT. For example, a wireless device may measure a plurality of downlink reference signals (SSBs or CSI-RS s, if CSI-RS is configured by RRC). The wireless device may select two or more SSBs by comparing RSRPs of the plurality of downlink reference signals and a threshold. For example, the threshold may comprise rsrp-ThresholdSSB when the plurality of downlink reference signals are SSBs. For example, the threshold may comprise rsrp-ThresholdCSl-RS when the plurality of downlink reference signals are CSI-RS s. For example, the wireless device may select two or more downlink referencing signals (SSBs or CSI-RS s) whose RSRPs are higher than the threshold. For example, if SSBs are configured with the wireless device, the wireless device may determine one or more PRACH occasions associated with the selected two or more downlink reference signals, e.g., SSBs. For example, the wireless device may determine the one or more PRACH based on an association between PRACH occasions and SSBs that may be indicated by one or more RRC parameters, e.g., ra-ssb-OccasionMaskIndex. For example, if CSI-RS s are configured with the wireless device, the wireless device may determine one or more PRACH occasions associated with the selected two or more downlink reference signals, e.g., CSI-RS s. For example, the wireless device may determine the one or more PRACH based on an association between PRACH occasions and CSI-RS s that may be indicated by one or more RRC parameters, e.g., ra-OccasionList.

FIG. 30 is an example of an association between DL reference signals and PRACH occasions. For example, the association may be one-to-one mapping, multi-to-one mapping between DL reference signals and PRACH occasions. For example, in FIG. 30, a wireless device measures k DL reference signals, and select DL reference signal 1, DL reference signal 2, and DL reference signal 3. For example, if PRACH occasion 1, PRACH occasion 2, and PRACH occasion 3 are associated with DL reference signal 1, DL reference signal 2, and DL reference signal 3, respectively, the wireless device may perform at most 3 LBTs, each LBT is performed prior to each of selected PRACH occasions. For example, a type of LBT may be pre-defined and/or semi-statically by a base station. For example, a base station may indicate a type of LBT of PRACH occasions in a RACH configuration. The type may be one of CAT 1, CAT 2, CAT 3, CAT 4 (or long LBT and/or short LBT).

For example, if an LBT succeed (channel is idle) in a first PRACH occasion, a wireless device may transmit one or more preambles via the first PRACH occasion and may not perform one or more LBTs in other PRACH occasions that may be available after the first PRACH occasions in the same PRACH burst. The wireless device may select a PRACH occasion based on a DL reference signal that the wireless device selects. The DL reference signal may be selected based on a measured received signal, random selection, etc. The wireless device may selection one or more DL reference signals thereby select one or more PRACH occasions associated with the one or more DL reference signals. For example, if a wireless device selects PRACH occasion 1, PRACH occasion 3, and LBT on PRACH occasion 1 is successful, the wireless device may not perform another LBT on PRACH occasion 3. For example, if a wireless device selects all PRACH occasions in Freq.1 in FIG. 30, the wireless device may perform one or more LBTs prior to each of PRACH occasions in Freq. 1 until an LBT is successful. In response to the LBT being successful, the wireless device may transmit one or more preambles associated with a PRACH occasion where the LBT was successful. The wireless device may transmit one or more preambles via one or more PRACH occasions selected based on one or more DL reference signals associated with the one or more PRACH occasions.

For example, if one or more PRACH occasions are FDMed, e.g., PRACH occasion1 and PRACH occasion 2 in FIG. 30, a wireless device may perform one LBT for the one or more PRACH occasions FDMed, which may be firstly available and/or may be randomly selected. For example, a wireless device may, based on RSRPs of DL reference signals, select PRACH occasion 1 and PRACH occasion 2 FDMed. In this case, the wireless device may perform LBTs on PRACH occasion 1 and PRACH occasion 2. If both LBTs are successful, the wireless device may randomly select one of them. For example, if both LBTs are successful, the wireless device may select one available first in time domain. For example, if both LBTs are successful, the wireless device may select one whose corresponding DL reference signal's RSRP is higher than the others. For example, PRACH occasion 1 and PRACH occasion 2 are FDMed within a threshold (less than a bandwidth threshold), the wireless device may perform a wideband LBT that may cover frequency range of PRACH occasion 1 and PRACH occasion2. In this case if the wideband LBT is successful, the wireless device may select one of PRACH occasions based on a random selection, time location of PRACH occasions, and/or RSRPs of corresponding DL reference signals as described in this paragraph.

For example, a wireless device may perform a long LBT on a first PRACH occasion firstly available and perform a short LBT on a second PRACH occasion followed by the first PRACH occasion if the LBT on the first PRACH occasion is failed, e.g., long LBT for PRACH occasion 1 and short LBT for PRACH occasion 3 in FIG. 30. For example, a type of LBT on the second PRACH occasion may be configured by a base station. For example, a type of LBT on the second PRACH occasion may be determined by a time difference of two PRACH occasions. For example, the first PRACH occasion and the second PRACH occasion has a guard time less than a threshold (configurable or pre-defined, e.g., 25 us,or 16 us), the wireless device may perform a short LBT on the second PRACH occasion, otherwise perform a long LBT.

For example, based on RSRPs of DL reference signals, a wireless device may select two or more PRACH occasions. For example, FIG. 30, a wireless device may select PRACH occasion 1, PRACH occasion 2, PRACH occasion 3. Then the wireless device may perform a first LBT on a first PRACH occasion available firstly in time, e.g., PRACH occasion1. The wireless device may determine a second LBT on a second PRACH occasion in response to the first LBT. For example, if the first LBT was successful, the wireless device may transmit a preamble via the first PRACH occasion. If the first LBT was not successful, the wireless device may determine to perform a second LBT on a second PRACH occasion available firstly after the first PRACH occasion, e.g., PRACH occasion 2. A third LBT on a third RACH occasion may be performed if the second LBT on the second PRACH occasion is failed. For example, the one or more FDMed PRACH occasions are configured within a guard time less than a threshold, the wireless device may perform a wideband LBT, LBTs on all of the one or more FDMed PRACH occasions.

In an example, a wireless device may transmit a plurality of preambles via a plurality of PRACH occasions. In an example, FIG. 30 is an example of one or more PRACH occasion configurations. For example, on Freq 1 in FIG. 30, PRACH occasions may be TDMed with a guard time (e.g., a time difference). In this case, a wireless device may perform an LBT in each PRACH occasions in Freq 1 for multiple preamble transmissions. For example, depending on the guard time between two PRACH occasions, a wireless device may perform a long LBT and/or short LBT. For example, if the guard time (time difference) is less than a threshold (25 us or 16 us), a wireless device may perform a short LBT (or no LBT) on a PRACH occasion available later than the other, otherwise the wireless device may perform long LBT. The type of LBT in each PRACH occasion may be configured by an RRC. The type of LBT in each PRACH occasion may be determined by a wireless device by comparing with a guard time between PRACH occasions and the threshold.

For example, on Freq 2 in FIG. 30, one or more PRACH occasions may be TDMed without a guard time (or less than a threshold). In this case, a wireless device may perform an LBT on the first PRACH occasion occurs firstly among the selected PRACH occasions in Freq 2. For the subsequent PRACH occasions followed by the first PRACH occasion in Freq 2, a wireless device may not perform an LBT if the LBT on the first PRACH occasion was successful. In an example, the LBT on the first PRACH occasion may be a long LBT. An LBT on the subsequent PRACH occasions may be a short LBT if the LBT on the first PRACH occasion was successful. If the selected PRACH occasions are not contiguous in time, a wireless device may perform a long LBT or a short LBT. For example, a type of LBT is configured by a base station or determined based on a time difference of the selected PRACH occasions non-contiguous. For example, on Freq 3 in FIG. 31, one or more PRACH occasions may be grouped without a guard time. For example, there may be a guard time between two groups as shown in PRACH occasion f3-2 and PRACH occasion f3-3 in FIG. 31. Similar mechanism determining an LBT in Freq. 2 and Freq.1 may be applied to the grouped PRACH occasions in other frequency bands.

The following descriptions may be aspects of one or more embodiments of the present disclosure. The following descriptions may be based on one or more operations in unlicensed band as an example. The following descriptions may be applied to one or more operations in licensed band if an LBT is omitted from the following examples.

A wireless device may switch a type of a RA procedure, e.g., the RA procedure is performed in an unlicensed band. In an example, a wireless device may switch a RA procedure from a contention-based (or contention-free) random access procedure in FIG. 25 to a two-step random access procedure in FIG. 26. There may be one or more ways that a wireless device performs the switching.

For example, for contention-based RA procedure and contention-free RA procedure, a wireless device may determine a retransmission of preamble. This may be because no RAR is detected during an RAR window or none of one or more RARs detected during the RAR window does not comprise a preamble index matched to a preamble that a wireless device. A wireless device may determine a retransmission of preamble for a contention-based RA procedure in FIG. 12 and/or FIG. 25 if a wireless device does not receive Msg4 from a base station. For example, once Msg 3 is transmitted, a wireless device may start a contention resolution timer (e.g., ra-ContentionResolutionTimer) or restart the contention resolution timer (e.g., ra-ContentionResolutionTimer) at each HARQ retransmission, e.g., in the first symbol after the end of the Msg 3 transmission. While the contention resolution timer is running, a wireless device may monitor a downlink control channel (e.g., PDCCH). A wireless device may stop the contention resolution timer and determine that the random access procedure successfully completed, e.g., based on the PDCCH transmission addressed by an RNTI assigned by a base station (e.g., C-RNTI and/or Temporary C-RNTI). If the contention resolution timer expires, the wireless device may perform at least one of following: determine the Contention Resolution not successful; flush the HARQ buffer used for transmission of the MAC PDU in the Msg 3 buffer; increment PREAMBLE_TRANSMISSION_COUNTER by 1; and/or perform a retransmission of preamble (e.g., perform Random Access Resource selection procedure).

For example, a wireless device may switch a type of RA procedure in a licensed band. For example, a wireless device may reduce a latency required in RA procedure based on the switching. For example, a wireless device may switch from a four-step contention based RA procedure to a two-step RA procedure, e.g., based on a retransmission of preamble being determined during the four-step contention based RA procedure.

FIG. 32A is an example of switching a type of RA procedure. For example, the first type RACH may be a contention-based random access procedure in FIG. 12 or contention-free random access procedure without LBTs in FIG. 25, and the second type RACH may be a two-step random access procedure in FIG. 16. For example, the first type RACH may be a two-step random access procedure in FIG. 16, and the second type RACH may be a contention-based random access procedure in FIG. 12 or contention-free random access procedure without LBTs in FIG. 25. For example, in FIG. 32A, a first (or second) type RACH may comprise one or more RACH resources if the first (or second) type RACH is configured for the contention-based (or contention-free) random access procedure. For example, in FIG. 32A, the first (or second, respectively) type RACH may comprise one or more RACH resources and one or more UL radio resources if the first (or second, respectively) type RACH is a two-step RA procedure in FIG. 16. If a wireless device determines a retransmission of preamble in a first type RACH, the wireless device may switch a type of RA procedure to a second type RACH if a transmission occasion of the second RACH occurs earlier than a transmission occasions of the first type RACH.

FIG. 32B is an example of switching a type of RA procedure in an unlicensed band. For example, the first type RACH and the second type RACH in FIG. 32B may requires at least one LBT. For example, the first type RACH may be a contention-based random access procedure in FIG. 25 or contention-free random access procedure in FIG. 25, and the second type RACH may be a two-step random access procedure in FIG. 26. For example, the first type RACH may be a two-step random access procedure in FIG. 26, and the second type RACH may be a contention-based random access procedure in FIG. 25 or contention-free random access procedure in FIG. 25. For example, in FIG. 32B, a first (or second) type RACH may comprise one or more RACH resources if the first (or second) type RACH is configured for the contention-based (or contention-free) random access procedure. For example, in FIG. 32B, the first (or second, respectively) type RACH may comprise one or more RACH resources and one or more UL radio resources if the first (or second, respectively) type RACH is configured for a two-step RA procedure in FIG. 26.

In FIG. 32B, for a retransmission of a preamble, a wireless device may select a type of RA procedure based on timing of a transmission occasion and a result of LBT. For example, a wireless device may perform an LBT in the order of transmission occasions in time of the first type RACH and the second type RACH. The wireless device may select a RA procedure based on the LBT procedure being successful (e.g., indicating idle). For example, in FIG. 32B, the wireless device may switch a type of RA procedure to a second type RACH if a second transmission occasion of the second RACH occurs earlier than a first transmission occasions of the first type RACH and/or an LBT procedure performed before the second transmission occasions is idle. For example, a wireless device may perform one or more LBT procedures in the order of transmission occasions of associated RACHs. For example, a wireless device may first perform an LBT procedure 3210. If the result is idle, a wireless device may switch a type to the second type RACH that may be a second type RACH 3220. The wireless device may perform a retransmission of a preamble on an associated RACH resources of the second type RACH 3220. If a result of LBT procedure 3210 is busy, a wireless device may perform a next available LBT procedure, that may be an LBT procedure 3230. If the next available LBT procedure (e.g., LBT procedure 3230) indicates idle, the wireless device may perform the retransmission of a preamble on an associated RACH resources, that may be a first type RACH 3240. If the LBT procedure 3230 indicates busy, the wireless device may perform a next available LBT procedure, that may be an LBT procedure 3250 in FIG. 32B, and so on (e.g., perform an LBT procedure 3270 in FIG. 32B). Depending on a result (idle/busy) of an LBT procedure and a type of RACH for which the LBT procedure is performed, the RA procedure may be switched to another or may remain the same.

In an example, FIG. 32B may be an example of RA procedure with multi-beam operation. For example, for a retransmission of a preamble, a wireless device may measure one or more DL reference signals (e.g., SSB and/or CSI-RS). The wireless device may select one or more DL reference signals (e.g., based on measured received signal power and/or based on a random selection), the wireless device may have one or more opportunities to perform the retransmission of the preamble. For example, in FIG. 32B, a wireless device may select one or more DL reference signals. RA configurations transmitted by a base station may indicate one or more association between the selected one or more DL references signals and one or more RACH radio resources. For example, the one or more radio resources comprise a first type RACH and/or a second type RACH. The radio resources (e.g., a first type RACH 3240, a first type RACH 3280, a second type RACH 3220, and/or a second type RACH 3260) may be associated with the one or more DL reference signals. For example, with the radio resources associated the selected one or more DL reference signals, the wireless device may select one of radio resources based on the method described above.

A base station may configure a wireless device with two RA configurations. The two RA configuration may comprise a two-step RA procedure, and/or contention-based RA procedure (e.g., contention-based four-step RA procedure). The two RA configuration may comprise a two-step RA procedure, and/or contention free RA procedure (e.g., contention free four-step RA procedure). For example, the two RA configuration may be configured with a wireless device when a TA value stored in a wireless device may be valid (e.g., in a small cell). For example, the two RA configuration may be configured with a wireless device when a wireless device may be in a first RRC state. For example, the first state may be RRC INACTIVE and/or RRC CONNECTED. A wireless device configured with the two RA configurations may be able to switch a type of RA procedure described above.

In an example, a wireless device may not perform a two-step RA procedure. For example, if a wireless device is in RRC IDLE, the wireless device may perform a four-step RA procedure in FIG. 12 and/or FIG. 25. For example, if a wireless device has no valid TA, the wireless device may perform a four-step RA procedure in FIG. 12 and/or FIG. 25.

In an existing technology, a wireless device may not switch a type of an RA procedure (e.g., from a four-step RA procedure in FIG. 12 or FIG. 25 to a two-step RA procedure in FIG. 16 or FIG. 26 or vice versa). A wireless device may select a type of an RA procedure in response to initiating the RA procedure. For example, a type of an RA procedure may be (re)selected after or in response to a first RA procedure determined unsuccessfully complete in an existing technology. For example, the wireless device may (re)select the type of the RA procedure as a part of another RA procedure (e.g., a second RA procedure) performed after the first RA procedure determined unsuccessfully complete (e.g., and/or in response to initiating the second RA procedure). For example, the four-step RA procedure in FIG. 12 and/or FIG. 25 may take 14 TTIs to complete the procedure. For example, the four-step RA procedure in FIG. 25 may take longer than 14 TTIs if at least one of LBT procedure in any UL and/or DL transmission in FIG. 25 determines that a channel for the UL and/or DL transmission is busy (occupied). There may be a need to enhance a performance (e.g., latency) of a four-step RA procedure in FIG. 12 and/or FIG. 25. In example embodiments, a wireless device may switch a type of an RA procedure based on one or more conditions for switching a type of an RA procedure. For example, the one or more conditions comprise at least one of: whether and/or when a valid TA value is available to a wireless device; what is an RRC state of a wireless device; in which procedure a wireless device performs in an RA procedure; and/or combination thereof. For example, the wireless device may switch a type of an RA procedure based on a valid TA value available. For example, the wireless device may determine to switch to a two-step RA procedure (e.g., FIG. 16 and/or FIG. 26) in response to a valid TA value being available. For example, the wireless device may switch to a two-step RA procedure (e.g., FIG. 16 and/or FIG. 26) based on a wireless device being with a particular RRC state (e.g., RRC IDLE, RRC CONNECTED, and/or RRC INACTIVE). Any combination is not limited. For example, a wireless device determines to switch to a two-step RA procedure (e.g., FIG. 16 and/or FIG. 26) based on a valid TA value being available and/or a particular RRC state of the wireless device. Switching to a two-step RA procedure from a four-step CBRA and/or two-step CFRA in FIG. 12 and/or FIG. 25 may reduce a latency. The reduce latency may result in a smaller number of transmissions and/or receptions, which leads to reduce a wireless device's battery power consumption.

For example, a wireless device may initiate an RA procedure with a four-step RA procedure (e.g., CBRA and/or CFRA) in FIG. 12 (or FIG. 25). This may be because the wireless device may be in RRC IDLE, and/or the wireless device may not have a valid TA. The wireless device may determine a retransmission of a preamble (e.g., determine to perform a random access resource selection procedure). If the wireless device determines the retransmission after receiving at least one RAR comprising a preamble index matched to a preamble that the wireless device transmits to a base station, the wireless device may switch an RA procedure to a two-step RA procedure.

For example, the wireless device may initiate a four step RA procedure (e.g., CBRA and/or CFRA) and transmit at least one preamble. The wireless device may receive at least one corresponding RAR and may transmit Msg 3 (e.g., Msg 3 1240 in FIG. 12 for an licensed band scenario or Msg 3 2540 in FIG. 25 for an unlicensed band scenario) to a base station. For example, the at least one corresponding RAR may comprise a TA command indicating a TA value and/or an RNTI (e.g., Temporary C-RNTI). For the case of the unlicensed band scenario, the wireless device may transmit the Msg 3 in response to receiving the at least one corresponding RAR and/or in response to a result of LBT procedure performed before Msg 3 transmission being idle. The wireless device may start a contention resolution timer (e.g., ra-ContentionResolutionTimer) or restart the contention resolution timer (e.g., ra-ContentionResolutionTimer) at each HARQ retransmission, e.g., in the first symbol after the end of the Msg 3 transmission. While the contention resolution timer is running, a wireless device may monitor a downlink control channel (e.g., PDCCH). If the PDCCH transmission is addressed by a particular RNTI assigned by a base station (e.g., C-RNTI assigned by a control message (e.g., RRC)), a wireless device may stop the contention resolution timer and determine that the random access procedure successfully completed. For example, contention resolution may be based on a contention resolution identity on DL-SCH. For example, if a base station assigns a C-RNTI to a wireless device, the wireless device may perform contention resolution based on a reception of a PDCCH transmission that is addressed to the C-RNTI. In response to detection of a C-RNTI on a PDCCH, a wireless device may determine the contention resolution successful and may determine a random access procedure successfully completed. If a wireless device has no valid C-RNTI, a contention resolution may be addressed by employing a TC-RNTI. For example, if a MAC PDU is successfully decoded and an MAC PDU comprises a contention resolution identity that matches the CCCH SDU transmitted in Msg 3, a wireless device may determine the contention resolution successful and may determine the random access procedure successfully completed.

If the contention resolution timer expires (e.g., the contention resolution is determined as completed unsuccessfully), the wireless device may perform at least one of following: determine the Contention Resolution not successful; flush the HARQ buffer used for transmission of the MAC PDU in the Msg 3 buffer; increment PREAMBLE_TRANSMISSION_COUNTER by 1; and/or perform a retransmission of preamble (e.g., perform Random Access Resource selection procedure). If the wireless device determines to perform a retransmission of preamble, the wireless device may switch an RA procedure with the TA value indicated by the at least one corresponding RAR. The wireless device may employ the TA value for transmitting one or more TBs in the two-step RA procedure. For example, the one or more TBs comprise Msg 3 that a wireless device transmitted in the four-step RA procedure. An RV pattern of Msg 3 may be RRC-configured in the RA configuration.

FIG. 33 is an example of a type of an RA procedure. A wireless device may receive, e.g., from a base station, message(s) indicating RA configuration(s). For example, the message(s) may be RRC message(s), PDCCH order, and/or a combination thereof. The RA configuration(s) may comprise one or more parameters for four-step RA procedure and/or for two-step RA procedure. The wireless device may initiate a four-step RA procedure. The wireless device may not have a valid TA value. For example, the TA timer of the wireless device expires. The wireless device may not be eligible (or may not allowed) to initiate a two-step RA procedure based on one or more conditions. For example, the wireless device is in a particular RRC state, e.g., RRC IDLE. For example, the wireless device does not have a valid TA value. The wireless device may transmit an Msg 1 (e.g., at least one preamble). The wireless device may receive an Msg 2 (e.g., RAR) corresponding to the Msg 1. For example, the Msg 2 may comprise one or more fields indicating at least one of: a TA command indicating a TA value, a particular RNTI (e.g., TC-RNTI), an uplink grant, and/or a preamble index matched to the preamble (e.g., the at least one preamble) that the wireless device transmits via the Msg 1. The wireless device may transmit an Msg 3 based on the one or more fields. The wireless device may determine that a contention resolution is failed (e.g., a contention resolution completes unsuccessfully). For example, the wireless device may determine that a contention resolution is failed based on a contention resolution is not resolved during a time interval (e.g., during a contention resolution timer running). The wireless device may switch a type of an RA procedure from the four-step RA procedure to a two-step RA procedure. Switching the type of the RA procedure may be based on a valid TA value available. For example, the valid TA value is a value indicated by the TA command in the Msg 2 (e.g., RAR). The wireless device may transmit two step Msg 1 3820 (e.g., preamble and one or more transport bocks) after or in response to the switching the type of the RA procedure. A uplink transmission timing of the two step Msg 1 3820 may be adjusted based on the valid TA value.

FIG. 34 is an example of a RA procedure switching from a four-step RA procedure to a two-step RA procedure. A wireless device may initiate a four-step RA procedure. The wireless device may receive at least one RAR corresponding to at least one preamble transmitted by the wireless device. The at least one RAR may comprise a TA value and/or an UL grant. The wireless device may transmit Msg 3 to the base station. The Msg 3 may be transmitted via resource(s) indicated by the UL grant. The uplink transmission timing of the Msg 3 may be adjusted based on the TA value. The wireless device may start a contention resolution timer in response to transmitting the Msg 3, and start to monitor PDCCH. If the wireless device does not receive PDCCH addressed by an RNTI (e.g., that may be RRC configured (e.g., C-RNTI) and/or RAR indicated (e.g., Temporary C-RNTI), the wireless device may determine a retransmission of a preamble. If the wireless device has a two-step RA configuration (e.g., configured by RRC message transmitted by the base station), the wireless device may start the preamble transmission as a part of the two-step RA configuration (e.g., a type of RA configuration is switched). A uplink transmission timing of the two step Msg 1 3920 may be adjusted based on the TA value indicated by the RAR. For example, a uplink transmission timing of at least one transport block of the two step Msg 1 3920 may be based on the TA value.

In an example, if a wireless device switches a type of RA procedure from a first type to a second type based on one or more combinations of any method described above, one or more RA parameters may be reset to initial value(s). For example, the one or more RA parameters may be at least one of following: PREAMBLE_TRANSMISSION_COUNTER, PREAMBLE_POWER_RAMPING_COUNTER, PREAMBLE_RECEIVED_TARGET_POWER.

In an example, if a wireless device switches a type of RA procedure from a first type to a second type based on one or more combinations of any method described above, one or more RA parameters maintained in the first type may be inherited to the second type. For example, the one or more RA parameters may be at least one of following: PREAMBLE_TRANSMISSION_COUNTER, PREAMBLE_POWER_RAMPING_COUNTER, PREAMBLE_RECEIVED_TARGET_POWER.

In an example, a wireless device may receive, from a base station, a message comprising configuration parameters indicating: one or more first random access channels of a first type random access procedure; one or more first preambles of the first type random access procedure; one or more second random access channels of a second type random access procedure; one or more second preambles of the second type random access procedure; and a first uplink resource of the second type random access procedure. For example, the wireless device may transmit, via at least first random access channel of the one or more first random access channels, at least one first preamble of the one or more first preambles to initiate the first type random access procedure. For example, the wireless device may receive a random access response corresponding to the at least one first preamble. For example, the random access response comprises an uplink grant and a timing advanced value. For example, the wireless device may transmit, via a second uplink resource indicated by the uplink grant, a message based on the timing advance value. For example, the wireless device may receive no contention resolution message corresponding to the message. For example, to initiate the second type random access procedure, the wireless device may transmit: at least second preamble of the one or more first preambles, via at least second random access channel of the one or more second random access channels; and one or more data packets, via a first uplink resource, based on the timing advanced value. In an example, the one or more first random access channels may be configured in a unlicensed band. In an example, the one or more second random access channels may be configured in a unlicensed band. In an example, the first uplink resource may be configured in an unlicensed band. In an example, the second uplink resource may be configured in an unlicensed band. In an example, the wireless device may transmit the at least one first preamble in response to a success of a second listen-before-talk. In an example, the wireless device may transmit the at least one second preamble in response to a success of a second listen-before-talk. In an example, the wireless device may transmit the one or more data packets in response to a success of a second listen-before-talk. In an example, the wireless device may increment a preamble transmission counter (e.g., at least one of following: PREAMBLE_TRANSMISSION_COUNTER, PREAMBLE_POWER_RAMPING_COUNTER, PREAMBLE_RECEIVED_TARGET_POWER) in response to transmitting the at least second preamble. In an example, the wireless device may reset a preamble transmission counter (e.g., at least one of following: PREAMBLE_TRANSMISSION_ COUNTER, PREAMBLE_POWER_RAMPING_ COUNTER, PREAMBLE_RECEIVED_TARGET_POWER) in response to transmitting the at least second preamble.

According to various embodiments, a device such as, for example, a wireless device, off-network wireless device, a base station, and/or the like, may comprise one or more processors and memory. The memory may store instructions that, when executed by the one or more processors, cause the device to perform a series of actions. Embodiments of example actions are illustrated in the accompanying figures and specification. Features from various embodiments may be combined to create yet further embodiments.

FIG. 35 is a flowchart as per an aspect of an example embodiment of the present disclosure. At 3510, a wireless device may receive first parameters and second parameters. The first parameters may indicate a first random access channel of a first type random access. The second parameters may indicate a second random access channel. The second parameters may indicate an uplink resource of a second type random access. At 3520, the wireless device may transmit a first preamble via the first random access channel. At 3530, the wireless device may receive a response. The response may indicate an index of the first preamble. The response may indicate a timing advance value. The response may indicate an uplink grant. The timing advance value and the uplink grant may be for a contention resolution. At 3540, the wireless device may transmit, based on a determination that the contention resolution is unsuccessfully completed, a second preamble; and a transport block. the second preamble may be transmitted via the second random access channel. The transport block may be transmitted via the uplink resource. The transport block may be transmitted based on the timing advance value.

According to an example embodiment, the wireless device may transmit the first preamble based on a control message received from a base station. According to an example embodiment, the control message may be a downlink control information. The downlink control information may indicate the first type random access. According to an example embodiment, the control message may be a radio resource configuration message. The radio resource configuration message may indicate the first type random access. According to an example embodiment, the wireless device may transmit the first preamble may be based on an unavailability of a valid timing advance value. According to an example embodiment, the unavailability of a valid timing advance value may be determined based on not receiving a timing advance command during a first time interval. According to an example embodiment, the unavailability of a valid timing advance value may be determined based on having not received a timing advance command. According to an example embodiment, the first type random access may be a four-step random access procedure. According to an example embodiment, the second type random access may be a two-step random access procedure. The wireless device may transmit a second transport block based on the timing advance value and the uplink grant. The second transport block may be for the contention resolution. The wireless device may receive no indication (e.g., no response) of the second transport block (e.g., for the contention resolution) during a contention resolution time interval. The determination that the contention resolution is unsuccessfully completed may be based on no indication (e.g., no response) of the second transport block (e.g., for the contention resolution) during a contention resolution time interval. According to an example embodiment, a transmission power of the second preamble may be determined based on a counter (e.g., a preamble power ramping counter). According to an example embodiment, the wireless device may increment the counter (e.g., the preamble power ramping counter) based on the determination of the contention resolution unsuccessfully completed. According to an example embodiment, the wireless device may reset the counter (e.g., the preamble power ramping counter) based on the determination of the contention resolution unsuccessfully completed. According to an example embodiment, the wireless device may monitor, during a random access response window, a downlink control channel for a second response corresponding to the second preamble and the transport block. According to an example embodiment, the random access response window may start in response to transmitting the transport block. According to an example embodiment, the second preamble and the transport block may be transmitted as a first uplink transmission (e.g., Msg A) of a two-step random access procedure. According to an example embodiment, the first random access channel may be configured in an unlicensed band. According to an example embodiment, the second random access channel and the uplink resource may be configured in an unlicensed band. According to an example embodiment, the wireless device may be in a radio resource configuration idle state. According to an example embodiment, the wireless device may be in a radio resource configuration connected state.

In an example, a wireless device may receive first parameters indicating a first random access channel of a first type random access. The wireless device may receive second parameters indicating a second random access channel and an uplink resource. The second random access channel and the uplink resource may be for a second type random access. The wireless device may transmit, to a base station, a first preamble via the first random access channel. The wireless device may receive a response. The response may indicate an identifier of the first preamble. The response may indicate a timing advance value and an uplink grant. The timing advance value and the uplink grant may be for a contention resolution. The wireless device may determine the contention resolution is unsuccessfully completed. The wireless device may transmit a second preamble via the second random access channel. The wireless device may transmit a transport block via the uplink resource. The transport block may be transmitted based on the timing advance value. The wireless device may transmit the second preamble and the transport block based on the contention resolution being unsuccessfully completed. The wireless device may transmit the second preamble and the transport block further based on an radio resource configuration state of the wireless device. According to an example embodiment, the radio resource configuration state is an radio resource configuration idle state. According to an example embodiment, the radio resource configuration state is an radio resource configuration connected state. According to an example embodiment, the radio resource configuration state is an radio resource configuration inactive state.

FIG. 36 is a flowchart as per an aspect of an example embodiment of the present disclosure. At 3610, a wireless device may perform a first type random access to a base station. At 3620, the wireless device may receive a response to the first type random access. The response may indicate a timing advance value and an uplink grant. The timing advance value and the uplink grant may be for a contention resolution. At 3630, the wireless device may perform the contention resolution based on the timing advance value and the uplink grant. At 3640, the wireless device may switch, based on the contention resolution being unsuccessful, to a second type random access to the base station.

FIG. 37 is a flowchart as per an aspect of an example embodiment of the present disclosure. At 3710, a base station may transmit, to a wireless device: first parameters indicating a first random access channel. The first random access channel may be for a first type random access. The base station may transmit, to the wireless device, second parameters indicating a second random access channel and an uplink resource. The second random access channel and the uplink resource may be for a second type random access. At 3720, the base station may receive, for example from the wireless device, a first preamble via the first random access channel. At 3730, the base station may transmit a response to the wireless device. The response may indicate an index of the first preamble. The response may further indicate a timing advance value and an uplink grant for a contention resolution. At 3740, the base station may determine that the contention resolution is unsuccessfully completed. The contention resolution may be performed, by the wireless device, based on the timing advance value and the uplink grant. At 3750, the base station may receive, from the wireless device and based on the determining, one or more uplink signals of the second type random access.

According to an example embodiment, the base station may transmit a control message to the wireless device. The base station may receive the first preamble based on the control message transmitted to the wireless device. According to an example embodiment, the control message may be a downlink control information indicating the first type random access. According to an example embodiment, the control message may be a radio resource configuration message indicating the first type random access. According to an example embodiment, the base station may receive the first preamble based on an unavailability of a valid timing advance value. According to an example embodiment, the base station may determine the unavailability of a valid timing advance value based on not transmitting, to the wireless device, a timing advance command during a first time interval. According to an example embodiment, the base station may determine the unavailability of a valid timing advance value based on having not transmitted, to the wireless device, a timing advance command. According to an example embodiment, the first type random access may be a four-step random access procedure. According to an example embodiment, the second type random access may be a two-step random access procedure. According to an example embodiment, the one or more uplink signals may be received with a received signal strength determined based on a preamble power ramping counter. According to an example embodiment, the preamble power ramping counter may be incremented in response to the contention resolution being unsuccessfully completed. According to an example embodiment, the preamble power ramping counter may be reset based on the contention resolution being unsuccessfully completed. According to an example embodiment, the base station may transmit, to the wireless device and during a random access response window, a second response corresponding to the one or more uplink signals. According to an example embodiment, the random access response window may start in response to receiving a transport block of the one or more uplink signals. According to an example embodiment, the one or more uplink signals may be determined based on one or more listen-before-talk procedures performed for the one or more uplink signals. According to an example embodiment, the one or more uplink signals may comprise a second preamble via the second random access channel; and a transport block, via the uplink resource, based on the timing advance value. According to an example embodiment, the one or more uplink signals may comprise a second preamble via the second random access channel. According to an example embodiment, the one or more listen-before-talk procedures performed for the second preamble may indicate that a channel (e.g., for a transmission of the second preamble) is sensed to be idle. According to an example embodiment, the one or more uplink signals may comprise a transport block, via the uplink resource, based on the timing advance value. According to an example embodiment, the one or more listen-before-talk procedures performed for the transport block may indicate that a channel (e.g., for a transmission of the transport block) is sensed to be idle. According to an example embodiment, the one or more uplink signals may comprise: a second preamble via the second random access channel; and a transport block, via the uplink resource, based on the timing advance value. According to an example embodiment, the one or more listen-before-talk procedures performed for the second preamble and/or the transport block may indicate that channel(s) (e.g., for a transmission of the second preamble and/or the transport block) are sensed to be idle. According to an example embodiment, the first random access channel may be configured in an unlicensed band. According to an example embodiment, the second random access channel and the uplink resource may be configured in an unlicensed band. According to an example embodiment, the base station may determine that the wireless device is in a radio resource configuration idle state. According to an example embodiment, the base station may determine that the wireless device is in a radio resource configuration connected state.

Embodiments may be configured to operate as needed. The disclosed mechanism may be performed when certain criteria are met, for example, in a wireless device, a base station, a radio environment, a network, a combination of the above, and/or the like. Example criteria may be based, at least in part, on for example, wireless device or network node configurations, traffic load, initial system set up, packet sizes, traffic characteristics, a combination of the above, and/or the like. When the one or more criteria are met, various example embodiments may be applied. Therefore, it may be possible to implement example embodiments that selectively implement disclosed protocols.

A base station may communicate with a mix of wireless devices. Wireless devices and/or base stations may support multiple technologies, and/or multiple releases of the same technology. Wireless devices may have some specific capability(ies) depending on wireless device category and/or capability(ies). A base station may comprise multiple sectors. When this disclosure refers to a base station communicating with a plurality of wireless devices, this disclosure may refer to a subset of the total wireless devices in a coverage area. This disclosure may refer to, for example, a plurality of wireless devices of a given LTE or 5G release with a given capability and in a given sector of the base station. The plurality of wireless devices in this disclosure may refer to a selected plurality of wireless devices, and/or a subset of total wireless devices in a coverage area which perform according to disclosed methods, and/or the like. There may be a plurality of base stations or a plurality of wireless devices in a coverage area that may not comply with the disclosed methods, for example, because those wireless devices or base stations perform based on older releases of LTE or 5G technology.

In this disclosure, “a” and “an” and similar phrases are to be interpreted as “at least one” and “one or more.” Similarly, any term that ends with the suffix “(s)” is to be interpreted as “at least one” and “one or more.” In this disclosure, the term “may” is to be interpreted as “may, for example.” In other words, the term “may” is indicative that the phrase following the term “may” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments.

If A and B are sets and every element of A is also an element of B, A is called a subset of B. In this specification, only non-empty sets and subsets are considered. For example, possible subsets of B={cell1, cell2} are: {cell1},{cell2}, and {cell1, cell2}. The phrase “based on” (or equally “based at least on”) is indicative that the phrase following the term “based on” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “in response to” (or equally “in response at least to”) is indicative that the phrase following the phrase “in response to” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “depending on” (or equally “depending at least to”) is indicative that the phrase following the phrase “depending on” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “employing/using” (or equally “employing/using at least”) is indicative that the phrase following the phrase “employing/using” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments.

The term configured may relate to the capacity of a device whether the device is in an operational or non-operational state. Configured may also refer to specific settings in a device that effect the operational characteristics of the device whether the device is in an operational or non-operational state. In other words, the hardware, software, firmware, registers, memory values, and/or the like may be “configured” within a device, whether the device is in an operational or nonoperational state, to provide the device with specific characteristics. Terms such as “a control message to cause in a device” may mean that a control message has parameters that may be used to configure specific characteristics or may be used to implement certain actions in the device, whether the device is in an operational or non-operational state

In this disclosure, various embodiments are disclosed. Limitations, features, and/or elements from the disclosed example embodiments may be combined to create further embodiments within the scope of the disclosure.

In this disclosure, parameters (or equally called, fields, or Information elements: IEs) may comprise one or more information objects, and an information object may comprise one or more other objects. For example, if parameter (IE) N comprises parameter (IE) M, and parameter (IE) M comprises parameter (IE) K, and parameter (IE) K comprises parameter (information element) J. Then, for example, N comprises K, and N comprises J. In an example embodiment, when one or more (or at least one) message(s) comprise a plurality of parameters, it implies that a parameter in the plurality of parameters is in at least one of the one or more messages, but does not have to be in each of the one or more messages. In an example embodiment, when one or more (or at least one) message(s) indicate a value, event and/or condition, it implies that the value, event and/or condition is indicated by at least one of the one or more messages, but does not have to be indicated by each of the one or more messages.

Furthermore, many features presented above are described as being optional through the use of “may” or the use of parentheses. For the sake of brevity and legibility, the present disclosure does not explicitly recite each and every permutation that may be obtained by choosing from the set of optional features. However, the present disclosure is to be interpreted as explicitly disclosing all such permutations. For example, a system described as having three optional features may be embodied in seven different ways, namely with just one of the three possible features, with any two of the three possible features or with all three of the three possible features.

Many of the elements described in the disclosed embodiments may be implemented as modules. A module is defined here as an element that performs a defined function and has a defined interface to other elements. The modules described in this disclosure may be implemented in hardware, software in combination with hardware, firmware, wetware (i.e. hardware with a biological element) or a combination thereof, all of which may be behaviorally equivalent. For example, modules may be implemented as a software routine written in a computer language configured to be executed by a hardware machine (such as C, C++, Fortran, Java, Basic, Matlab or the like) or a modeling/simulation program such as Simulink, Stateflow, GNU Octave, or Lab VIEWMathScript. Additionally, it may be possible to implement modules using physical hardware that incorporates discrete or programmable analog, digital and/or quantum hardware. Examples of programmable hardware comprise: computers, microcontrollers, microprocessors, application-specific integrated circuits (ASICs); field programmable gate arrays (FPGAs); and complex programmable logic devices (CPLDs). Computers, microcontrollers and microprocessors are programmed using languages such as assembly, C, C++ or the like. FPGAs, ASICs and CPLDs are often programmed using hardware description languages (HDL) such as VHSIC hardware description language (VHDL) or Verilog that configure connections between internal hardware modules with lesser functionality on a programmable device. The above mentioned technologies are often used in combination to achieve the result of a functional module.

The disclosure of this patent document incorporates material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, for the limited purposes required by law, but otherwise reserves all copyright rights whatsoever.

While various embodiments have been described above, it should be understood that they have been presented by way of example, and not limitation. It will be apparent to persons skilled in the relevant art(s) that various changes in form and detail can be made therein without departing from the scope. In fact, after reading the above description, it will be apparent to one skilled in the relevant art(s) how to implement alternative embodiments. Thus, the present embodiments should not be limited by any of the above described exemplary embodiments.

In addition, it should be understood that any figures which highlight the functionality and advantages, are presented for example purposes only. The disclosed architecture is sufficiently flexible and configurable, such that it may be utilized in ways other than that shown. For example, the actions listed in any flowchart may be re-ordered or only optionally used in some embodiments.

Further, the purpose of the Abstract of the Disclosure is to enable the U.S. Patent and Trademark Office and the public generally, and especially the scientists, engineers and practitioners in the art who are not familiar with patent or legal terms or phraseology, to determine quickly from a cursory inspection the nature and essence of the technical disclosure of the application. The Abstract of the Disclosure is not intended to be limiting as to the scope in any way.

Finally, it is the applicant's intent that only claims that include the express language “means for” or “step for” be interpreted under 35 U.S.C. 112. Claims that do not expressly include the phrase “means for” or “step for” are not to be interpreted under 35 U.S.C. 112. 

What is claimed is:
 1. A method comprising: receiving, by a wireless device, a random access response in response to transmitting a first random access preamble, the random access response comprising an uplink grant; transmitting, via the uplink grant, a Msg 3 message comprising a wireless device identifier of the wireless device; starting a contention resolution time window based on transmitting the Msg 3 message; determining a contention resolution is unsuccessful in response to not receiving a response, comprising the wireless device identifier and corresponding to the Msg 3 message, during the contention resolution time window; and based on the determining, performing a two-step random access procedure comprising transmitting a message comprising: a second random access preamble via a random access channel resource; and a transport block via an uplink resource corresponding to the random access channel resource.
 2. The method of claim 1, wherein the random access response is received during a random access response window.
 3. The method of claim 1, wherein the performing the two-step random access procedure further comprises selecting the second random access preamble from one or more preambles.
 4. The method of claim 1, wherein the Msg 3 message is transmitted for requesting one of: an establishment of a radio resource control connection; a reestablishment of the radio resource control connection; or a resumption of the radio resource control connection.
 5. The method of claim 1, wherein the response, corresponding to the Msg 3 message, is a contention resolution identity medium access control control element (MAC CE) comprising a contention resolution identity that matches the wireless device identifier.
 6. The method of claim 1, wherein the wireless device identifier is a cell radio network identifier indicated by a cell radio network identifier medium access control control element (MAC CE).
 7. The method of claim 6, wherein the response, corresponding to the Msg 3 message, comprises a downlink control channel transmission addressed to the cell radio network identifier.
 8. The method of claim 1, wherein the transport block comprises a cell radio network identifier medium access control control element (MAC CE) indicating the wireless device identifier.
 9. The method of claim 1, wherein the transport block comprises the wireless device identifier for requesting one of: an establishment of a radio resource control connection; a reestablishment of the radio resource control connection; or a resumption of a suspended the radio resource control connection.
 10. The method of claim 1, further comprising starting a two-step random access response time window based on transmitting the transport block.
 11. A wireless device comprising: one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the wireless device to: receive a random access response in response to transmitting a first random access preamble, the random access response comprising an uplink grant; transmit, via the uplink grant, a Msg 3 message comprising a wireless device identifier of the wireless device; start a contention resolution time window based on transmitting the Msg 3 message; determine a contention resolution is unsuccessful in response to not receiving a response, comprising the wireless device identifier and corresponding to the Msg 3 message, during the contention resolution time window; and based on the determination, perform a two-step random access procedure comprising transmitting a message comprising: a second random access preamble via a random access channel resource; and a transport block via an uplink resource corresponding to the random access channel resource.
 12. The wireless device of claim 11, wherein the random access response is received during a random access response window.
 13. The wireless device of claim 11, wherein to perform the two-step random access procedure, the instructions further cause the wireless device to select the second random access preamble from one or more preambles.
 14. The wireless device of claim 11, wherein the Msg 3 message is transmitted for requesting one of: an establishment of a radio resource control connection; a reestablishment of the radio resource control connection; or a resumption of the radio resource control connection; and wherein the transport block comprises the wireless device identifier for requesting one of: the establishment of the radio resource control connection; the reestablishment of the radio resource control connection; or the resumption of the suspended the radio resource control connection.
 15. The wireless device of claim 11, wherein the response, corresponding to the Msg 3 message, is a contention resolution identity medium access control control element (MAC CE) comprising a contention resolution identity that matches the wireless device identifier.
 16. The wireless device of claim 11, wherein the wireless device identifier is a cell radio network identifier indicated by a cell radio network identifier medium access control control element (MAC CE).
 17. The wireless device of claim 16, wherein the response, corresponding to the Msg 3 message, comprises a downlink control channel transmission addressed to the cell radio network identifier.
 18. The wireless device of claim 11, wherein the transport block comprises a cell radio network identifier medium access control control element (MAC CE) indicating the wireless device identifier.
 19. The wireless device of claim 11, wherein the instructions further cause the wireless device to start a two-step random access response time window based on transmitting the transport block.
 20. A system comprising: a base station comprising one or more first processors and first memory storing first instructions that, when executed by the one or more first processors, cause the base station to: transmit a random access response in response to receiving a first random access preamble, the random access response comprising an uplink grant; receive, via the uplink grant, a Msg 3 message comprising a wireless device identifier of a wireless device; and receive in a message: a second random access preamble via a random access channel resource; and a transport block via an uplink resource corresponding to the random access channel resource; and the wireless device comprising one or more second processors and second memory storing second instructions that, when executed by the one or more second processors, cause the wireless device to: receive the random access response in response to transmitting the random access preamble, the random access response comprising the uplink grant; transmit, via the uplink grant, the Msg 3 message comprising the wireless device identifier of the wireless device; start a contention resolution time window based on transmitting the Msg 3 message; determine a contention resolution is unsuccessful in response to not receiving a response, comprising the wireless device identifier and corresponding to the Msg 3 message, during the contention resolution time window; and based on the determination, perform a two-step random access procedure comprising transmitting the message comprising: the second random access preamble via the random access channel resource; and the transport block via the uplink resource corresponding to the random access channel resource. 